Wearable camera system, and video recording control method for wearable camera system

ABSTRACT

A wearable camera system includes a wearable camera, an in-car recorder, and an in-car camera. One of the in-car recorder and the wearable camera transmits video recording starting information including information indicating that video recording has been started to the other of the in-car recorder and the wearable camera when one of the in-car recorder and the wearable camera starts the video recording. The other of the in-car recorder and the wearable camera starts video recording after the video recording starting information is received.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a wearable camera system, and a videorecording control method for the wearable camera system. The presentinvention relates to a wearable camera system including an imagecapturing device, for example, which can be mounted on a human body orworn clothes, and a video recording control method therefor.

2. Description of the Related Art

In recent years, introduction of a wearable camera which is mounted on apolice officer or a security guard and is used in order to supportduties of the police officer or the security guard, for example, hasbeen taken into consideration.

As an example of the related art using the wearable camera, JapanesePatent Unexamined Publication No. 2006-148842 discloses a wearablemonitoring camera system, for example. The wearable monitoring camerasystem has a configuration in which a video signal and an audio signalfrom body-mounted CCD camera means and microphone means, and a date andtime information signal from built-in clock means are encoded by encodeserver means which is accommodated in body-mounted pouch means, and thedate and time information converted into character information can berecorded by being superimposed on a captured video.

In this system, for example, in a case where a police officer or asecurity guard wears and uses a wearable camera, it is expected thatrecording of video data (video signal) is started by the police officeror the security guard pressing a recording button.

However, if the police officer or the security guard attempts to handlean emergency situation, there is a possibility of being incapable ofperforming a video recording start operation, and thus a state may occurin which an important scene for the future incident investigation is notrecorded (recording omission). Paying attention to the video recordingstart operation may decrease the attention of the police officer or thesecurity guard to the emergency situation. Also in a case where anin-car camera is mounted in a patrol car or the like and can performvideo recording, the video recording start operation may not beperformed and thus recording omission may occur in the same manner.

SUMMARY OF THE INVENTION

The present invention has been made in consideration of the abovecircumstances, and an object thereof is to provide a wearable camerasystem and a video recording control method therefor capable ofimproving convenience in treating video data captured by a wearablecamera or an in-car camera and thus of reducing recording omission ofthe video data.

A wearable camera system of the present invention includes a wearablecamera that can be mounted on a user; an in-car recorder that isequipped in a vehicle in which the user rides; and an in-car camerawhich is equipped in the vehicle. The in-car camera includes a firstcapture that captures videos. The in-car recorder includes a firstcommunicator that performs communication with the wearable camera as acommunication partner; and a first recorder that records first videodata captured by the in-car camera. The wearable camera includes asecond capture that captures videos; a second communicator that performscommunication with the in-car recorder as a communication partner; and asecond recorder that records second video data captured by the secondcapture. One of the in-car recorder and the wearable camera transmitsvideo recording starting information including information indicatingthat video recording has been started to the other of the in-carrecorder and the wearable camera when one of the in-car recorder and thewearable camera starts the video recording. The other of the in-carrecorder and the wearable camera starts video recording after the videorecording starting information is received.

A video recording control method of the present invention is a videorecording control method for a wearable camera system including awearable camera that can be mounted on a user; an in-car recorder thatis equipped in a vehicle in which the user rides; and an in-car camerawhich is equipped in the vehicle, the method including causing thein-car camera to capture videos and causing the wearable camera tocapture videos; causing the in-car recorder to record first video datacaptured by the in-car camera and causing the wearable camera to recordsecond video data captured by the wearable camera; and performingcommunication between the in-car recorder and the wearable camera. Inthe recording of the videos, video recording is started by one of thein-car recorder and the wearable camera, and in the performing ofcommunication, one of the in-car recorder and the wearable cameratransmits video recording starting information including informationindicating that video recording has been started to the other of thein-car recorder and the wearable camera when one of the in-car recorderand the wearable camera starts the video recording. In the recording ofthe videos, the other of the in-car recorder and the wearable camerastarts video recording after the video recording starting information isreceived. According to the present invention, it is possible to improveconvenience of handling video data captured by a wearable camera or anin-car camera and thus to reduce recording omission of the video data.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an explanatory diagram regarding an overview of a wearablecamera system and usage of video data captured by a wearable camera,according to an exemplary embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating that a police officer ridesin a patrol car and goes to a scene in the exemplary embodiment of thepresent invention;

FIG. 3 is a block diagram illustrating an example of an internalconfiguration of the wearable camera according to the exemplaryembodiment of the present invention;

FIG. 4 is a diagram illustrating a state in which a user wears thewearable camera according to the exemplary embodiment of the presentinvention;

FIG. 5 is a front view illustrating an example of the appearance of thewearable camera according to the exemplary embodiment of the presentinvention;

FIG. 6 is a left side view illustrating an example of the appearance ofthe wearable camera according to the exemplary embodiment of the presentinvention;

FIG. 7 is a right side view illustrating an example of the appearance ofthe wearable camera according to the exemplary embodiment of the presentinvention;

FIG. 8 is a block diagram illustrating an example of an internalconfiguration of an in-car recorder according to the exemplaryembodiment of the present invention;

FIG. 9 is a block diagram illustrating an example of an internalconfiguration of an in-car PC according to the exemplary embodiment ofthe present invention;

FIG. 10 is a schematic diagram illustrating an example of setting ofattribute information according to the exemplary embodiment of thepresent invention;

FIG. 11 is a schematic diagram illustrating an example of a datastructure of video recording data according to the exemplary embodimentof the present invention;

FIG. 12 is a schematic diagram illustrating an example of a datastructure of a recorded video list held in the wearable camera accordingto the exemplary embodiment of the present invention;

FIG. 13 is a schematic diagram illustrating an example of a datastructure of a recorded video list held in the in-car recorder accordingto the exemplary embodiment of the present invention;

FIG. 14 is a sequence diagram illustrating an operation example of thewearable camera system in a case where the wearable camera starts videorecording through in-car system conjunction according to the exemplaryembodiment of the present invention;

FIG. 15 is a sequence diagram illustrating an operation example of thewearable camera system in a case where the in-car system starts videorecording through wearable camera (WCAM) conjunction according to theexemplary embodiment of the present invention;

FIG. 16 is a flowchart illustrating an example of a procedure regardingan attribute information assigning operation in the wearable cameraaccording to the exemplary embodiment of the present invention;

FIG. 17 is a flowchart illustrating an operation example in a case wherea specific wearable camera is searched for as a communication partner byan in-car recorder according to a second exemplary embodiment of thepresent invention;

FIG. 18 is a schematic diagram illustrating an example of a managementtable in which information regarding the specific wearable cameraderived as a communication partner is held according to the secondexemplary embodiment of the present invention;

FIG. 19 is a flowchart illustrating an operation example in a case wherea specific in-car recorder is searched for as a communication partner bya wearable camera according to the second exemplary embodiment of thepresent invention;

FIG. 20 is a sequence diagram illustrating an operation example of thewearable camera system in a case where the wearable camera starts videorecording through in-car system conjunction according to the secondexemplary embodiment of the present invention;

FIG. 21 is a sequence diagram illustrating an operation example of thewearable camera system in a case where an in-car recorder starts videorecording through WCAM conjunction according to the second exemplaryembodiment of the present invention;

FIG. 22 is a schematic diagram illustrating an example of attributeinformation in a wearable camera according to a third exemplaryembodiment of the present invention;

FIG. 23 is a schematic diagram illustrating an example of attributeinformation in an in-car recorder according to the third exemplaryembodiment of the present invention;

FIG. 24 is a schematic diagram illustrating an example of a datastructure of video recording data according to the third exemplaryembodiment of the present invention;

FIG. 25 is a schematic diagram illustrating an example of a datastructure of a recorded video list held in the wearable camera accordingto the third exemplary embodiment of the present invention;

FIG. 26 is a schematic diagram illustrating an example of a datastructure of a recorded video list held in the in-car recorder accordingto the third exemplary embodiment of the present invention;

FIG. 27 is a sequence diagram illustrating a first example of anattribute information assigning procedure in a wearable camera systemaccording to the third exemplary embodiment;

FIG. 28 is a sequence diagram illustrating a second example of anattribute information assigning procedure in the wearable camera systemaccording to the third exemplary embodiment;

FIG. 29 is a sequence diagram illustrating a third example of anattribute information assigning procedure in the wearable camera systemaccording to the third exemplary embodiment; and

FIG. 30 is a sequence diagram illustrating a fourth example of anattribute information assigning procedure in the wearable camera systemaccording to the third exemplary embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, exemplary embodiments of the present invention will bedescribed with reference to the drawings.

FIG. 1 is an explanatory diagram regarding an overview of wearablecamera system 100 and usage of video data captured by wearable camera 10according to the present exemplary embodiment. FIG. 2 is a schematicdiagram illustrating that police officer 7 rides in patrol car 6 andgoes to scene 8.

Wearable camera 10 of the present exemplary embodiment is an imagecapturing device which can be mounted on the body or worn clothes of auser (for example, police officer 7 or a security guard). Wearablecamera 10 has a communication function of performing communication within-car system 60 equipped in a car and servers (back-end servers) SV1,SV2 and SV3 in a user's organization.

In wearable camera system 100, front-end system 100A is configured toinclude wearable camera 10, and in-car system 60, and back-end system100B is configured to include management software 70 on a network,in-station PC 71 which is a PC used in police station 5, and serversSV1, SV2, and SV3. Management software 70 is executed by, for example,in-station PC 71 or servers SV1 to SV3.

Here, a description will be made assuming a case of being used in policestation 5, as an example of the wearable camera system 100. In thiscase, police officer 7 performs image capturing by using wearable camera10. For example, captured video data is transmitted to back-end system100B in police station 5 and is accumulated therein. In wearable camera10, a user is not limited to police officer 7. Wearable camera 10 mayalso be used in other various places of work (for example, a securitycompany). In the present exemplary embodiment, police officer 7 will bemainly exemplified as a user.

Front-end system 100A includes wearable camera 10 which can be mountedon police officer 7 who is dispatched to the front lines of scene 8, andin-car system 60 which is installed in patrol car 6.

In-car system 60 includes in-car camera 61, in-car recorder 62, in-carPC 63, a communication unit, and the like, thereby configuring an in-carcamera system, a video management system, and the like (refer to FIG.2).

In-car camera 61 includes a capture which is installed at apredetermined position of patrol car 6 and captures videos of theperiphery of patrol car 6 at all times or at predetermined timings.In-car camera 61 includes, for example, a front camera which captures animage of the front side of patrol car 6, and a back seat camera whichcaptures an image of a back seat (for example, a seat which a suspect isseated) in patrol car 6. Video data captured by in-car camera 61 isrecorded, for example, and is then accumulated in in-car recorder 62. Aplurality of in-car cameras 61 may be installed.

A microphone which collects sound inside and outside of patrol car 6 maybe provided in the front camera or the back seat camera. In this case,sound output by police officer 7 or a suspect in patrol car 6 can becollected (recorded).

In-car recorder 62 accumulates the video data captured by in-car camera61. In-car recorder 62 may assign meta information such as attributeinformation to the video data captured by in-car camera 61 and managethe video data.

In-car recorder 62 may acquire video data captured by wearable camera 10and accumulate the video data. Meta information such as attributeinformation may be assigned to acquired or accumulated video data.

In-car PC 63 may be not only a PC which is equipped in patrol car 6 in afixed manner but also a wireless communication device such as a portablePC, a smart phone, a mobile phone, a tablet terminal, or a personaldigital assistant (PDA) portable to the outside of patrol car 6.

In-car PC 63 executes the management software so as to cause in-carsystem 60 to cooperate with wearable camera 10. User interfaces (UIs)(for example, an operator, a display, and a sound output) of in-car PC63 may be used as UIs for operating in-car recorder 62.

When police officer 7 is dispatched from police station 5 to carry out apredetermined duty (for example, patrols), the police officer wearswearable camera 10, for example, rides in patrol car 6 equipped within-car system 60, and goes to scene 8 (refer to FIG. 2).

In front-end system 100A, for example, videos of scene 8 at which patrolcar 6 has arrived are captured by in-car camera 61 of in-car system 60,and police officer 7 steps out of patrol car 6. Then, more detailedvideos of scene 8 are captured by wearable camera 10.

Video data such as moving images and still images captured by wearablecamera 10 are stored in, for example, a memory of wearable camera 10, ora memory of in-car recorder 62 or in-car PC 63 of in-car system 60.

Wearable camera 10 transmits (uploads) various pieces of data includingthe video data captured by wearable camera 10 from the memory or thelike of wearable camera 10 to back-end system 100B.

In-car system 60 (for example, in-car recorder 62) transmits (uploads)various pieces of data including the video data captured by in-carcamera 61 from the memory or the like of in-car system 60 to back-endsystem 100B.

Transmission of the data to back-end system 100B is performed throughconnection using wireless communication from scene 8, or is performedusing wired communication or wireless communication, or in a manualmanner (for example, through a hand-carried storage medium) when thepolice officer returns to police station 5 after completing the patrols.

Back-end system 100B includes servers SV1 to SV3 which are installed inpolice station 5 or other places, management software 70 for performingcommunication with front-end system 100A, and in-station PC 71.

Servers SV1 to SV3 are provided with a storage such as a hard disk drive(HDD) or a solid state driver (SSD) inside or outside servers SV1 toSV3. Servers SV1 to SV3 accumulate video data and other data transmittedfrom front-end system 100A therein. Servers SV1 to SV3 receive videodata transmitted from, for example, wearable camera 10 or in-car system60 (for example, in-car recorder 62), and preserves the video data inthe storage such as an HDD.

The video data accumulated in back-end system 100B is used for handlingor investigation of an incident by a person in charge in the relevantdepartment of police station 5, for example. As necessary, the videodata is copied into a predetermined storage medium (for example, adigital versatile disk (DVD)) and is submitted to a predetermined scene(for example, trial) as evidence. In the present exemplary embodiment,the evidential videos of scene 8 can be more exactly acquired andpreserved by using wearable camera 10 worn by police officer 7.

In order for police officer 7 to be dispatched to scene 8 from policestation 5 and to use wearable camera 10, identification information (forexample, an officer ID) of police officer 7, identification information(for example, a camera ID) of wearable camera 10 used by police officer7, identification information (for example, a car ID) of patrol car 6used by police officer 7, and the like are set and registered by usingin-station PC 71 or the like. Consequently, when, by which policeofficer, and with which camera the video data accumulated in servers SV1to SV3 was captured can be clearly discriminated.

The setting and registration of police officer 7 or wearable camera 10are performed, for example, by a person in charge in police station 5 orpolice officer 7 who is being dispatched operating the operator ofin-station PC 71, and by PC 71 executing management software 70. In thesetting and registration, information other than the above-describedofficer ID, camera ID, and car ID may be input via the operator ofin-station PC 71.

In other words, management software 70 includes, for example, anapplication for managing members of police officers 7, an applicationfor managing allocation of patrol cars 6, or the like, and anapplication for managing take-out of wearable camera 10. Managementsoftware 70 includes, for example, an application for searching for andextracting specific video data from a plurality of items of video dataaccumulated in servers SV1 to SV3 on the basis of attribute information.

When police officer 7 rides in patrol car 6, police officer 7 can log into in-car system 60. When the login is performed, for example, theofficer ID, the camera ID, and other information are input by operatingthe operator of in-car PC 63 in the same manner as in the setting andregistration in police station 5. The input officer ID, camera ID, andother information are held in, for example, in-car recorder 62.

If police officer 7 logs in to in-car system 60, police officer 7 isallowed to use in-car system 60. Cooperation between in-car system 60and wearable camera 10 carried by police officer 7 may be possible afterthe login is performed. For example, video data captured by wearablecamera 10 may be transmitted to in-car system 60 (for example, in-carrecorder 62), police officer 7 may recognize the video data via in-carPC 63, and in-car system 60 (for example, in-car recorder 62) may givevarious setting instructions to wearable camera 10.

FIG. 3 is a block diagram illustrating an example of an internalconfiguration of wearable camera 10. FIG. 4 is a diagram illustrating astate where police officer 7 wears wearable camera 10. FIG. 5 is a frontview illustrating an example of the appearance of wearable camera 10.FIG. 6 is a left side view illustrating an example of the appearance ofwearable camera 10. FIG. 7 is a right side view illustrating an exampleof the appearance of wearable camera 10.

As illustrated in FIG. 3, wearable camera 10 includes capture 11,general purpose input/output (GPIO) 12, random access memory (RAM) 13,read only memory (ROM) 14, and storage 15. Wearable camera 10 includeselectrically erasable programmable read-only memory (EEPROM) 16, realtime clock (RTC) 17, and global positioning system (GPS) 18. Wearablecamera 10 includes micro controller unit (MCU) 19, communicator 21,universal serial bus (USB) 22, contact terminal 23, power source 24, andbattery 25.

As examples of operation input sections, wearable camera 10 includesvideo recording switch SW1, snapshot switch SW2, attribute informationassigning switch SW3, attribute selecting switch SW4, communication modeswitch SW5, and indicator switch SW6.

As examples of state displays, wearable camera 10 includes lightemitting diodes (LEDs) 26 a, 26 b, and 26 c, and vibrator 27.

Capture 11 includes, for example, image capturing lens 11 a (refer toFIG. 5) and a solid-state imaging device such as a charge coupleddevice-type (CCD) image sensor or a complementary metal oxidesemiconductor-type (CMOS) image sensor. Capture 11 outputs video data ofa subject obtained through image capturing to MCU 19.

GPIO 12 is a parallel interface through which signals are input andoutput between video recording switch SW1, snapshot switch SW2,attribute information assigning switch SW3, attribute selecting switchSW4, communication mode switch SW5, indicator switch SW6, LEDs 26 a to26 c, and vibrator 27; and MCU 19. GPIO 12 is connected to, for example,various sensors (for example, an acceleration sensor).

RAM 13 is a work memory which is used when MCU 19 operates. ROM 14 is amemory in which programs and data for controlling MCU 19 are stored inadvance.

Storage 15 is constituted of a storage medium such as an SD memory, andstores video data captured and obtained by capture 11. When the SDmemory is used as storage 15, the memory is attachable to and detachablefrom the casing main body of wearable camera 10.

EEPROM 16 stores, for example, identification information (a serialnumber as a camera ID) which identifies wearable camera 10, and othersetting information. The other setting information includes, forexample, login information (for example, a car ID and an officer ID)which is obtained through setting and registration in in-station PC 71or by logging in to in-car recorder 62, and correspondence informationindicating correspondence between a state of attribute selecting switchSW4 and attribute information.

RTC 17 counts current time information and outputs the information toMCU 19.

GPS 18 receives current positional information of wearable camera 10 andcurrent time information from a GPS transmitter and outputs theinformation to MCU 19. The time information is used to correct systemtime of the wearable camera.

MCU 19 functions as a controller so as to perform, for example, acontrol process for collectively controlling the entire operations ofthe respective units of wearable camera 10, data input and outputprocesses among the respective units of wearable camera 10, a datacalculation (computation) process, and a data storing process. MCU 19operates in accordance with the program and data stored in ROM 14. MCU19 uses, for example, RAM 13 during an operation, acquires current timeinformation from RTC 17, and acquires current positional informationfrom GPS 18.

For example, communicator 21 defines the connection between communicator21 and MCU 19 in a physical layer which is a first layer in an opensystems interconnection (OSI) reference model. Communicator 21 performswireless communication (for example, Wi-Fi (registered trademark))through a wireless LAN (W-LAN), for example, in accordance with thedefinition thereof. Communicator 21 may perform wireless communicationsuch as near field communication (NFC) or Bluetooth (registeredtrademark).

USB 22 is a serial bus which allows wearable camera 10 to be connectedto, for example, in-car system 60, or in-station PC 71 in police station5.

Contact terminal 23 is a terminal for being electrically connected witha cradle, an external adaptor, or the like. Contact terminal 23 isconnected to MCU 19 via USB 22, and is connected to power source 24.Charging of wearable camera 10 and communication of data including videodata can be performed via contact terminal 23.

For example, contact terminal 23 is provided with “charge terminal V+”,“CON.DET terminal”, “data terminals D- and D+”, and “a ground terminal”.CON.DET terminal is a terminal for detecting a voltage and a voltagechange. Data terminals D− and D+ are terminals for transmitting videodata or the like captured by wearable camera 10 to an external PC via,for example, a USB connector terminal.

Contact terminal 23 is connected to a cradle or a connector of anexternal adaptor, and thus data communication can be performed betweenwearable camera 10 and an external apparatus.

Power source 24 supplies source power supplied from a cradle or anexternal adaptor via, for example, contact terminal 23, to battery 25,thereby charging battery 25. Battery 25 is constituted of a rechargeablesecondary battery and supplies the source power to each of the units ofwearable camera 10.

Video recording switch SW1 is, for example, a push button switch used toinput an operational instruction for performing starting or stoppage ofvideo recording (capturing of a moving image) through a pressingoperation performed by police officer 7.

Snapshot switch SW2 is, for example, a push button switch used to inputan operational instruction for performing capturing of a still imagethrough a pressing operation performed by police officer 7.

Attribute information assigning switch SW3 is, for example, a pushbutton switch used to input an operational instruction for assigningattribute information to video data through a pressing operationperformed by police officer 7.

Attribute selecting switch SW4 is, for example, a slide switch used toinput an operational instruction for selecting an attribute to beassigned to video data.

Communication mode switch SW5 is, for example, a slide switch used toinput an operational instruction for setting a communication modebetween wearable camera 10 and an external apparatus.

Indicator switch SW6 is, for example, a slide switch used to input anoperational instruction for setting an operation state display modeusing LEDs 26 a to 26 c and vibrator 27. Video recording switch SW1,snapshot switch SW2, attribute information assigning switch SW3, andattribute selecting switch SW4 are configured to be able to be easilyoperated even in an emergency situation. Each of switches SW1 to SW6 isnot limited to the above-described forms. The switch may be an operationinput device in other forms allowing a user to input an operationalinstruction.

LED 26 a is a display indicating a power supply state (ON-OFF state) ofwearable camera 10 and a state of battery 25.

LED 26 b is a display indicating a state of the image capturingoperation (video recording state) of wearable camera 10.

LED 26 c is a display indicating a state of the communication mode ofwearable camera 10.

MCU 19 detects an input operation on each of the switches such as videorecording switch SW1, snapshot switch SW2, attribute informationassigning switch SW3, attribute selecting switch SW4, communication modeswitch SW5, and indicator switch SW6, and performs a process related toan input operation on the switch.

When an input operation on video recording switch SW1 is detected, MCU19 controls starting or stoppage of the image capturing operation incapture 11, and preserves video data obtained from capture 11 in storage15 as video data of a moving image.

When an input operation on snapshot switch SW2 is detected, MCU 19preserves video data obtained by capture 11 when snapshot switch SW2 isoperated in storage 15 as video data of a still image.

When an input operation on attribute information assigning switch SW3 isdetected, MCU 19 assigns attribute information which has been set inadvance to the video data, and preserves the information in storage 15by associating the information with the video data. In this case,association information indicating a correspondence relationship betweenthe state of attribute selecting switch SW4 and predetermined attributeinformation is held in EEPROM 16, and MCU 19 detects the state ofattribute selecting switch SW4, so as to assign attribute informationcorresponding to the setting for attribute selecting switch SW4.

MCU 19 detects the state of communication mode switch SW5 and operatescommunicator 21 in accordance with a communication mode corresponding tothe setting for communication mode switch SW5.

When a video recording operation starts, MCU 19 detects the state ofindicator switch SW6 and notifies the outside of the state of the videorecording operation through the LED display and/or vibrations of thevibrator, in accordance with the setting of indicator switch SW6.

As illustrated in FIG. 4, wearable camera 10 is used in a mounted stateon worn clothes or the body of police officer 7, for example, the chestof police officer 7 so as to capture a video in a viewing field from aposition close to the viewpoint of police officer 7. Police officer 7captures a subject on the periphery by operating video recording switchSW1 in a state of wearing wearable camera 10.

As illustrated in FIG. 5, in wearable camera 10, image capturing lens 11a of capture 11, video recording switch SW1, and snapshot switch SW2 areprovided on the front face of casing 10A having a substantiallyrectangular parallelepiped shape.

For example, video recording (capturing of a moving image) starts bypressing video recording switch SW1 an odd number of times, and thevideo recording ends by pressing the switch an even number of times.

Every time Snapshot switch SW2 is pressed, a still image at that momentis captured. As illustrated in FIG. 6, attribute information assigningswitch SW3, attribute selecting switch SW4, and USB connector 22 a areprovided on the left side of casing 10A of wearable camera 10 whenviewed from the front side thereof. As police officer 7 performs apressing operation on attribute information assigning switch SW3,attribute information corresponding to the setting state of attributeselecting switch SW4 is assigned to video data which is currently beingrecorded or video data which is recorded immediately before.

In the illustrated example, attribute selecting switch SW4 is a slideswitch having contact point positions of three stages C1, C2, and C3.Police officer 7 selects and designates attribute information which hasbeen allocated and set to each of stages C1 to C3.

A cable for being connected to an external apparatus through USB 22 isconnected to USB connector 22 a. Consequently, wearable camera 10 can beconnected to in-car system 60, in-station PC 71 or the like in policestation 5 so as to perform data communication.

As illustrated in FIG. 7, communication mode switch SW5 and indicatorswitch SW6 are provided on the right side of casing 10A of wearablecamera 10 when viewed from the front side thereof.

In the illustrated example, communication mode switch SW5 is a slideswitch having contact point positions of four stages AP, STA1, STA2, andOFF. The user selects and designates a communication mode of wearablecamera 10.

AP is an access point mode. In this mode, wearable camera 10 operates asan access point for the wireless LAN and is connected to a portableterminal carried by police officer 7 in a wireless manner so thatcommunication is performed between wearable camera 10 and the portableterminal.

In the access point mode, the portable terminal is connected to wearablecamera 10, and can thus display a current live video obtained bywearable camera 10, reproduce recorded video data, display a capturedstill image, and display attribute information or meta informationassigned to video data.

STA1 and STA2 are station modes. In these modes, communication isperformed with an external apparatus as an access point when connectionto the external apparatus is performed by using the wireless LAN. STA1is a mode for connection to an access point in police station 5, STA2 isa mode for connection to in-car system 60, and different connectiondestination information pieces are respectively set therefor.

In the station mode, wearable camera 10 can perform various settings andcan transmit (upload) the recroded video data preserved in wearablecamera 10 to in-car system 60, in-station PC 71 in police station 5, orservers SV1 to SV3.

OFF is a mode for turning off a communication operation using thewireless LAN. In this mode, the wireless LAN is not in use.

In the illustrated example, indicator switch SW6 is a slide switchhaving contact point positions of four stages of LED, Vibration, LED &Vibration, and OFF. Police officer 7 selects and designates thenotification mode of wearable camera 10.

LED is a mode for displaying an operation state of wearable camera 10 invideo-recording, for example, through LEDs 26 a to 26 c.

Vibration is a mode for performing a notification of an operation stateof wearable camera 10 through vibration of vibrator 27.

LED & Vibration is a mode for issuing notification of an operation stateof wearable camera 10 through the displaying of LEDs 26 a to 26 c andvibration of vibrator 27.

OFF is a mode for turning off a notification operation of an operationstate.

As illustrated in FIG. 4, LEDs 26 a to 26 c are disposed on the top facewhen viewed from the front side of casing 10A of wearable camera 10.Consequently, LEDs 26 a to 26 c can be easily and visually recognized bypolice officer 7 in a state of wearing wearable camera 10. No one elsemay see LEDs 26 a to 26 c except for police officer 7.

Contact terminal 23 is provided on the bottom face of casing 10A ofwearable camera 10 when viewed from the front side thereof.

FIG. 8 is a block diagram illustrating an example of an internalconfiguration of in-car recorder 62. In-car recorder 62 is configured toinclude CPU 101, wireless communicator 102, wired communicator 103,flash ROM 104, RAM 105, μCON 106, GPS 107, GPIO 108, buttons 109, LED110, and SSD 111.

CPU 101 performs, for example, a control process for collectivelycontrolling the entire operations of the respective units of in-carrecorder 62, data input and output processes with other units thereof, adata calculation (computation) process, and a data storing process.

Wireless communicator 102 performs wireless communication with anexternal device via a wireless line. The wireless communicationincludes, for example, a wireless local area network (LAN), near fieldcommunication (NFC), and Bluetooth (registered trademark). In thewireless LAN communication, communication is performed in accordancewith, for example, the IEEE802.11n standard of Wi-Fi (registeredtrademark).

CPU 101 and wireless communicator 102 are connected to each other via,for example, peripheral component interconnect (PCI) or a USB. Wirelesscommunicator 102 performs communication with, for example, in-car camera61, in-car PC 63, wearable camera 10, or in-station PC 71 or servers SV1to SV3 in police station 5.

Wired communicator 103 performs wired communication with an externaldevice via a wired line (for example, a wired LAN). Wired communicator103 performs wired communication with, for example, in-car camera 61,in-car PC 63, wearable camera 10, or in-station PC 71 or servers SV1 toSV3 in police station 5.

Flash ROM 104 is, for example, a memory which stores programs and datafor controlling CPU 101. Various pieces of setting information are heldtherein.

RAM 105 is, for example, a work memory used when CPU 101 operates. Forexample, a plurality of RAMs 105 are provided.

μCON 106 is one kind of microcomputer, and is connected to therespective units (for example, GPS 107, GPIO 108, buttons 109, and LED110) related to an external interface so as to perform control regardingthe external interface. μCON 106 is connected to CPU 101 via, forexample, a universal asynchronous receiver/transmitter (UART).

GPS 107 receives, for example, current position information of in-carrecorder 62 and current time information from a GPS transmitter, andoutputs the information to CPU 101. The time information is used tocorrect system time of in-car recorder 62.

GPIO 108 is a parallel interface. Signals are input and output betweenan external device which is connected via GPIO 108, and MCU 19. Forexample, various sensors (for example, a speed sensor, an accelerationsensor, and a door opening/closing sensor) are connected to GPIO 108.

Buttons 109 include, for example, a video recording button for startingor stopping recording of video data which is captured by in-car camera61, and an assigning button for assigning attribute information or metainformation to the video data captured by in-car camera 61.

LED 110 indicates, for example, a power supply state (ON-OFF state) ofin-car recorder 62, a video recording state, a state of in-car recorder62 being connected to the LAN, and a usage state of the LAN connected toin-car recorder 62, through lighting, putting-out, blinking, and thelike.

SSD 111 accumulates, for example, video data captured and recorded byin-car camera 61. SSD 111 may accumulate video data captured andrecorded by wearable camera 10. SSD 111 may accumulate data other thanvideo data. SSD 111 is connected to CPU 101 via serial ATA (SATA). SSD111 may be provided in a plurality. Storages (for example, an HDD) otherthan SSD 111 may be provided.

FIG. 9 is a block diagram illustrating an example of an internalconfiguration of in-car PC 63. In-car PC 63 is configured to include CPU201, input/output (I/O) controller 202, communicator 203, memory 204,input 205, display 206, speaker 207, and HDD 208. In-car PC 63 canperform communication with wearable camera 10 and in-car recorder 62,and can also perform communication with servers SV1 to SV3 of back-endsystem 100B or in-station PC 71.

CPU 201 performs, for example, a control process for collectivelycontrolling the entire operations of the respective units of in-car PC63, data input and output processes with other units thereof via I/Ocontroller 202, a data calculation (computation) process, and a datastoring process.

CPU 201 authenticates whether or not police officer 7 can log in toin-car system 60 through an input operation performed by police officer7 on a login screen to in-car system 60, displayed on display 206, forexample. The input operation performed by police officer 7 is anoperation of inputting, for example, an officer ID and a password.Various pieces of information regarding police officer 7 who is a targetto be allowed to log in are preserved in, for example, memory 204 inadvance. CPU 201 determines whether or not police officer 7 can log into in-car system 60 by using the information regarding a target to beallowed to log in, preserved in memory 204 in advance.

Regarding the login, login to in-car system 60 may be performed by usingin-car PC 63, and login to an application which is installed in in-carPC 63 and is used to operate in-car system 60 may be performed.

I/O controller 202 performs control regarding inputting and outputtingof data between CPU 201 and the respective units (for example,communicator 203, input 205, display 206, and speaker 207) of in-car PC63, so as to perform relay of data from CPU 201 and relay of data to CPU201. I/O controller 202 may be configured integrally with CPU 201.

Communicator 203 performs wired or wireless communication with, forexample, in-car recorder 62, wearable camera 10 worn by police officer7, or back-end system 100B side.

In a case where police officer 7 is logging in to in-car system 60,communicator 203 transmits the login information preserved in memory 204to wearable camera 10 so that the login information is copied. In a casewhere police officer 7 is not logging in to in-car system 60,communicator 203 does not transmit the login information to wearablecamera 10. The login information includes, for example, an officer IDfor identifying police officer 7, a camera ID for identifying wearablecamera 10, and a car ID for identifying patrol car 6 which is used.

Memory 204 is configured by using, for example, a RAM, a ROM, or anonvolatile or volatile semiconductor memory, functions as a work memorywhen CPU 201 operates, and preserves a predetermined program and datafor operating CPU 201. Memory 204 preserves, for example, logininformation regarding police officer 7 who is allowed to log in toin-car system 60.

Input 205 is a UI for notifying CPU 201 of an input operation frompolice officer 7 via I/O controller 202, and is a pointing device suchas a mouse or a keyboard. Input 205 may be configured by using, forexample, a touch panel or a touch pad which is disposed to correspond toa screen of display 206 and is operable with the finger of policeofficer 7 or a stylus pen.

Input 205 allows, for example, login information for logging in toin-car system 60 to be input.

Display 206 is configured by using, for example, a liquid crystaldisplay (LCD) or an organic electroluminescence (EL) display, anddisplays various pieces of information. For example, in a case wherevideo data captured (recorded) by wearable camera 10 is input inresponse to an input operation from police officer 7, display 206displays videos included in the video data on its screen under thecontrol of CPU 201.

For example, in a case where video data including sound, captured(recorded) by wearable camera 10 is input in response to an inputoperation from police officer 7, speaker 207 outputs the sound includedin the video data under the control of CPU 201. Display 206 and speaker207 may be configured separately from in-car PC 63.

HDD 208 stores, for example, various items of data and software(software programs). Specifically, HDD 208 preserves, for example,software for controlling or setting in-car recorder 62, and software forcontrolling or setting wearable camera 10. HDD 208 preserves, forexample, video data which is captured by wearable camera 10 and istransmitted from wearable camera 10.

Next, a description will be made of assignment of attribute informationto video data. In wearable camera system 100, a case is assumed in whichvideo data recorded by wearable camera 10 is transmitted to andaccumulated in servers SV1 to SV3, and is used. Similarly, a case isassumed in which video data captured by in-car camera 61 is recorded byin-car recorder 62 so as to be transmitted to and accumulated in serversSV1 to SV3, and is used.

In this case, for example, in-station PC 71 can extract and reproducetarget video data from the accumulated items of video data in responseto an operation performed by a police officer in police station 5 on thebasis of some sort of attribute information associated with video data,such as the type of video content, police officer 7 which has performedimage capturing, the date and time, and an image capturing location. Atthis time, attribute information correlated with the video data is used.As a result of the attribute information being assigned to the videodata, it is easy to discriminate captured videos from each other, andthus it becomes easier to extract target video data.

Here, wearable camera 10 assigns classification information (Classify)indicating the type of video content as the attribute information, andthe video data items can be individually sorted by the type. Theclassification information indicates an incident category regardingcontent of the video data. Assignment of the attribute information tothe video data is also referred to as tagging or the like. The attributeinformation is not limited to the classification information, andincludes all types of information regarding recorded video data. Theclassification information, which is the attribute information, may bearranged in hierarchical structure, or may be categorized in multiplesystems differently classified.

As mentioned above, in-car recorder 62 can assign classificationinformation (Classify) indicating the type of video content as theattribute information, and can individually sort the video data items bythe type.

FIG. 10 is a schematic diagram illustrating an example of settingattribute information to attribute selecting switch SW4. The attributeinformation is selected by operating attribute selecting switch SW4, andis assigned by operating attribute information assigning switch SW3.

In a case of using wearable camera 10, as illustrated in FIG. 10, theattribute information is allocated and is set so as to respectivelycorrespond to states (contact point positions) C1 to C3 of attributeselecting switch SW4. In the illustrated example, a case is assumed inwhich police officer 7 captures images of scene 8 (for example, anincident scene). Driving under the influence is allocated to C1; drugabuse violations are allocated to C2; and stolen property is allocatedto C3.

In the allocation of the attribute information, MCU 19 of wearablecamera 10 selects and sets attribute information which is frequentlyused by police officer 7 among a plurality of defined attributeinformation pieces. The set content of attribute information is storedin EEPROM 16 of wearable camera 10 as one of setting information pieces.

For example, communicator 203 acquires attribute information which isinput via input 205 of in-car PC 63, and CPU 101 assigns the acquiredattribute information to video data captured by in-car camera 61 byusing in-car recorder 62. In the assignment of the attribute informationusing in-car recorder 62, the number of contact points is not fixedunlike in attribute selecting switch SW4, and thus more types ofattribute information can be assigned.

FIG. 11 is a schematic diagram illustrating an example of a datastructure of video recording data. The video recording data includesrecorded video data and meta information corresponding to the videodata. The meta information includes attribute information as will bedescribed later. Video recording data which is captured and recorded bywearable camera 10 has the same format as that of video recording datawhich is captured by in-car camera 61 and is recorded by in-car recorder62.

Next, a description will be made of a data structure of a recorded videolist. A recorded video list associated with video data captured bywearable camera 10 is held in storage 15 of wearable camera 10. Arecorded video list associated with video data captured by in-car camera61 is held in SSD 111 of in-car recorder 62.

FIG. 12 is a schematic diagram illustrating an example of a datastructure of the recorded video list held in wearable camera 10.

If an input operation on attribute information assigning switch SW3 isdetected during video recording or after video recording, wearablecamera 10 generates attribute information associated with video data ofa video recording target and stores meta information including theattribute information in storage 15. In other words, video recordingdata stored in storage 15 includes the video data and the metainformation. In a case where the video data is transmitted to serversSV1 to SV3, wearable camera 10 transmits and accumulates the videorecording data including the video data and the meta information to andin servers SV1 to SV3. The video data and the meta information may betransmitted separately from each other.

The meta information associated with the video data is stored in a formof the recorded video list as illustrated in FIG. 12, for example. Themeta information of the recorded video list includes video positioninformation (video time information), a car ID, an officer ID, attributeinformation (incident category), a video recording starting factor, andother information.

The video data and the meta information are linked to each other byusing a video data ID. The video data ID is identification informationfor identifying recorded video data. The video data ID is assigned tothe video data, for example, at the time of starting video recording,during the video recording, or at the time of completing the videorecording. The video data ID includes, for example, recording start timeof the video data, a file name, and other IDs.

The video position information is information regarding time at whichthe meta information is assigned to the video data, that is, informationregarding time (also referred to as attribute information assigningtime) at which an input operation on attribute information assigningswitch SW3 is detected.

The car ID is identification information for identifying individualpatrol car 6. The officer ID is identification information foridentifying police officer 7 using wearable camera 10. By setting thecar ID and the officer ID, it is possible to discriminate which policeofficer 7 using which patrol car 6 has recorded the video data by usingwearable camera 10.

The incident category is classification information for identifying thetype of video data, and is assigned in accordance with attributeselecting switch SW4 on the basis of the set content of the attributeinformation illustrated in FIG. 10.

The video recording starting factor indicates a factor which causesrecording of the video data to be started. The video recording startingfactor includes, for example, detection of pressing of video recordingswitch SW1 or snapshot switch SW2, detection of a video recordingstarting trigger based on information from the sensor (for example, anacceleration sensor), RTC 17, or GPS 18 provided in wearable camera 10,and in-car system conjunction.

The in-car system conjunction indicates that wearable camera 10 startsvideo recording in response to a video recording starting instructionfrom in-car recorder 62 through cooperation between in-car system 60 andwearable camera 10.

The other information includes, for example, GPS information. The GPSinformation is position information indicating a location where thevideo data was recorded, and, for example, current position informationat the time of assigning the attribute information is acquired from GPS18 and is assigned as the GPS information.

The meta information assigned by wearable camera 10 is assigned throughprocessing in MCU 19, for example, and is stored in storage 15 inassociation with the video data captured by wearable camera 10.

One or more meta information pieces may be assigned to a single videodata item, that is, a single video data ID. For example, in a case wherepolice officer 7 observes the scene of drug abuse violations during acrackdown on driving under the influence, police officer 7 performs aninput operation on attribute information assigning switch SW3 twicewhile continuing to record video data, and thus wearable camera 10 canassign two meta information pieces to a single video data item.

FIG. 13 is a schematic diagram illustrating an example of a datastructure of the recorded video list held in in-car recorder 62.

The recorded video list held in in-car recorder 62 also includes metainformation including attribute information associated with video data.The content of the meta information is the same as the content of themeta information illustrated in FIG. 12.

However, in-car recorder 62 can assign more types of attributeinformation (incident category) than attribute information assigned bywearable camera 10. In in-car recorder 62, the video recording startingfactor includes detection of pressing of the attribute informationassigning button, detection of a video recording starting trigger basedon information from the sensors (for example, a speed sensor, anacceleration sensor, and a door opening/closing sensor) provided inin-car system 60, RTC 17, or GPS 107, and WCAM conjunction.

The WCAM conjunction indicates that in-car camera 61 has started videorecording under the instruction of in-car recorder 62 in response to avideo recording starting instruction from wearable camera 10 throughcooperation between in-car system 60 and wearable camera 10.

The meta information assigned by in-car recorder 62 is assigned throughprocessing in CPU 101, for example, and is stored in SSD 111 inassociation with the video data captured by in-car camera 61.

Next, an operation example of wearable camera system 100 will bedescribed.

FIG. 14 is a sequence diagram illustrating an operation example ofwearable camera system 100 in a case where wearable camera 10 startsvideo recording through the in-car system conjunction.

FIG. 14 exemplifies that in-car recorder 62 and wearable camera 10 areconnected to each other in a wireless manner via the wireless LAN, butthe recorder and the camera may be connected to each other in a wirelessmanner according to other methods, and may be connected to each other ina wired manner.

First, in-car recorder 62 and wearable camera 10 detect mutualcommunication partners so that a communication link between in-carrecorder 62 and wearable camera 10 is established (step S1).Specifically, CPU 101 of in-car recorder 62 and MCU 19 of wearablecamera 10 detect communication partners by performing a pairing processby using, for example, SSIDs and passwords for the wireless LAN.

Wireless communicator 102 of in-car recorder 62 and communicator 21 ofwearable camera 10 exchange, for example, car IDs and officer IDs whichare respectively held therein, and the communication link is establishedin a case where the car IDs and the officer IDs held in a host deviceand a communication partner device respectively match each other.

Wireless communicator 102 of in-car recorder 62 and communicator 21 ofwearable camera 10 may establish the communication link when detectingcommunication partners without checking matching of the camera IDs andthe officer IDs. For example, in a case where police officer 7 is notlogging in to in-car PC 63, the camera ID and the officer ID are notinput to in-car recorder 62, and thus the camera ID and the officer IDare not held in in-car recorder 62.

Even in this case, the communication link can be established betweenin-car system 60 and wearable camera 10. For example, even in a casewhere combinations of police officer 7 and a patrol car at the time ofdispatch differ every time and thus are not fixed, in-car recorder 62and wearable camera 10 can be easily connected to each other by usingthe wireless LAN or the like.

In in-car recorder 62, if a video recording starting trigger isdetected, CPU 101 starts recording of video data which is captured byin-car camera 61 and starts storing of the video data in SSD 111 (stepS2).

The video recording starting trigger in in-car recorder 62 includes, forexample, detection of pressing of buttons 109, detection of starting oflighting and ringing of patrol lamps of patrol car 6 in CPU 101,detection of a traveling speed of patrol car 6 being equal to or higherthan a predetermined speed (for example, 100 km/h) in the speed sensor,detection of an impact in the acceleration sensor (that is, detection ofa change in acceleration of a predetermined threshold value or greater),and detection of being out of a communication range in whichcommunication between wireless communicator 102 and wearable camera 10cannot be performed.

Wireless communicator 102 notifies wearable camera 10 as a communicationpartner of a video recording starting message (for example, a message“REC START”) including information indicating that video recording hasstarted when CPU 101 starts recording of video data (step S3).

In wearable camera 10, if communicator 21 receives the video recordingstarting message from in-car recorder 62, MCU 19 starts recording ofvideo data which is captured by capture 11 and starts storing of thevideo data in storage 15 (step S4).

As mentioned above, since video recording is started in wearable camera10 in conjunction with video recording starting in in-car recorder 62,for example, even in a case where police officer 7 forgets a videorecording starting operation on video recording switch SW1 or snapshotswitch SW2 of wearable camera 10 due to emergency response, video dataof scene 8 can be recorded and be checked in the future.

For example, in a case where in-car recorder 62 and wearable camera 10have a long distance therebetween and are thus out of a communicationrange using the wireless LAN when a video recording starting trigger isdetected, in-car recorder 62 may transmit a video recording startingmessage after the wireless connection is recovered.

Wearable camera 10 may not start video recording immediately afterreceiving the video recording starting message. For example, wearablecamera 10 may not start video recording when the video recordingstarting message is received during traveling of patrol car 6, and maystart video recording when detecting that the wireless connection within-car recorder 62 is canceled due to becoming distant from patrol car6. Consequently, it is possible to use a resource of storage 15 whichaccumulates recorded video data, with high efficiency.

After in-car recorder 62 and wearable camera 10 start video recording,if CPU 101 of in-car recorder 62 detects a video recording stoppingtrigger, CPU 101 stops recording of the video data captured by in-carcamera 61 and stops storing of the video data in SSD 111 (step S5).

The video recording stopping trigger in in-car recorder 62 includes, forexample, detection of pressing of buttons 109 in CPU 101 during videorecording, and detection of a predetermined time period elapsing fromthe video recording starting in in-car recorder 62.

Wireless communicator 102 of in-car recorder 62 notifies wearable camera10 as a communication partner of a video recording stopping message (forexample, a message “REC STOP”) including information indicating that thevideo recording has stopped when CPU 101 stops recording of video data(step S6).

In wearable camera 10, if communicator 21 receives the video recordingstopping message from in-car recorder 62, MCU 19 stops recording of thevideo data captured by capture 11 and stops storing of the video data instorage 15 (step S7).

As mentioned above, since video recording is stopped in wearable camera10 in conjunction with video recording stoppage in in-car recorder 62,for example, even in a case where police officer 7 forgets a videorecording stopping operation on video recording switch SW1 of wearablecamera 10 due to emergency response, video data of scene 8 can bestopped from being recorded. Therefore, it is possible to reduceunnecessary power consumption or unnecessary use of the memory due toforgetfulness of stopping of video data recording.

FIG. 14 exemplifies that in-car recorder 62 stops video recording andtransmits the recording stopping message in steps S5 and S6, andwearable camera 10 receives the video recording stopping message andstops video recording in step S7. Alternatively, wearable camera 10 maystop video recording and may transmit the video recording stoppingmessage in steps S5 and S6, and in-car recorder 62 may receive the videorecording stopping message and may stop video recording in step S7.

The processes in steps S5 to S7 may be omitted. In other words,cooperation for stopping video recording between in-car recorder 62 andwearable camera 10 may not be performed.

For example, in a case where in-car recorder 62 and wearable camera 10have a long distance therebetween and are thus out of a communicationrange using the wireless LAN when a video recording stopping trigger isdetected, in-car recorder 62 may transmit a video recording stoppingmessage after the wireless connection is recovered.

There may be a plurality of wearable cameras 10 which receive a videorecording starting message and start video recording. Similarly, theremay be a plurality of wearable cameras 10 which receive a videorecording stopping message and stop video recording. For example, it isassumed that a plurality of police officers 7 ride in patrol car 6.

FIG. 15 is a sequence diagram illustrating an operation example ofwearable camera system 100 in a case where in-car recorder 62 startsvideo recording through wearable camera (WCAM) conjunction. In theoperation example illustrated in FIG. 15, the same processes as in theoperation example illustrated in FIG. 14 are given the same stepnumbers, and description thereof will be omitted or will be madebriefly.

In wearable camera 10, if a video recording starting trigger isdetected, MCU 19 starts recording of video data which is captured bycapture 11 and starts storing of the video data in storage 15 (stepS2A).

The video recording starting trigger in wearable camera 10 includes, forexample, detection of pressing of video recording switch SW1 or snapshotswitch SW2 in MCU 19, detection of cancelation of wireless connectionbetween in-car recorder 62 and wearable camera 10 in MCU 19, detectionof an impact in the acceleration sensor (that is, detection of a changein acceleration of a predetermined threshold value or greater),detection of police officer 7 being present in a predetermined area inGPS 18, and detection of police officer 7 starting to run in GPS 18. Thedetection of an impact in the acceleration sensor includes detection ofpolice officer 7 starting to run and falling.

Communicator 21 notifies in-car recorder 62 as a communication partnerof a video recording starting message (for example, a message “RECSTART”) including information indicating that video recording has beenstarted when MCU 19 starts recording of video data (step S3A).

In in-car recorder 62, if wireless communicator 102 receives the videorecording starting message from wearable camera 10, CPU 101 startsrecording of video data which is captured by in-car camera 61 and startsstoring of the video data in SSD 111 (step S4A).

As mentioned above, since video recording is started in in-car recorder62 in conjunction with video recording starting in wearable camera 10,for example, even in a case where police officer 7 arrives at scene 8,then an incident occurs, and video recording is not started by in-carcamera 61 in patrol car 6, video data of scene 8 can be recorded byin-car camera 61 and be checked in the future.

After wearable camera 10 and in-car recorder 62 start video recording,if MCU 19 of wearable camera 10 detects a video recording stoppingtrigger, MCU 19 stops recording of the video data captured by capture 11and stops storing of the video data in storage 15 (step S5A).

The video recording stopping trigger in wearable camera 10 includes, forexample, detection of pressing of video recording switch SW1 in MCU 19during video recording, and detection of a predetermined time periodelapsing from the video recording starting in wearable camera 10.

Communicator 21 notifies in-car recorder 62 as a communication partnerof a video recording stopping message (for example, a message “RECSTOP”) including information indicating that the video recording hasstopped when MCU 19 stops recording of video data (step S6A).

In in-car recorder 62, if wireless communicator 102 receives the videorecording stopping message from wearable camera 10, CPU 101 stopsrecording of the video data captured by in-car camera 61 and stopsstoring of the video data in SSD 111 (step S7A).

As mentioned above, since video recording is stopped in in-car recorder62 in conjunction with video recording stoppage in wearable camera 10,for example, even in a case where police officer 7 forgets a pressingoperation of buttons 109 for stopping video recording, video datacaptured by in-car camera 61 can be stopped from being recorded.Therefore, it is possible to reduce unnecessary power consumption orunnecessary use of the memory due to forgetfulness of stopping of videodata recording.

FIG. 15 exemplifies that wearable camera 10 stops video recording andtransmits the video recording stopping message in steps S5A and S6A, andin-car recorder 62 receives the video recording stopping message andstops video recording in step S7A. Alternatively, in-car recorder 62 maystop video recording and may transmit the video recording stoppingmessage in steps S5A and S6A, and wearable camera 10 may receive thevideo recording stopping message and may stop video recording in stepS7A.

The processes in steps S5A to S7A may be omitted. In other words,cooperation for stopping video recording between wearable camera 10 andin-car recorder 62 may not be performed.

FIG. 16 is a flowchart illustrating an example of a procedure regardingan attribute information assigning operation performed by wearablecamera 10 of the present exemplary embodiment.

MCU 19 of wearable camera 10 performs initial setting prior to assigningof attribute information (step S11). The initial setting of wearablecamera 10 is performed by police officer 7 accessing in-station PC 71 inpolice station 5 and transmitting setting information through anoperation of in-station PC 71 when being dispatched.

The initial setting includes, for example, assigning of a camera ID andan officer ID, making attribute information assigning switch SW3 andattribute selecting switch SW4 activated, and allocating a plurality ofattribute information pieces to attribute selecting switch SW4 (refer toFIG. 10, for example).

If a video recording starting message is received from in-car recorder62, MCU 19 starts a video recording operation and stores video datacaptured by capture 11 in storage 15 (step S12). The video data hereinmay be a moving image and a still image.

If a video recording operation is started according to the videorecording starting message from in-car recorder 62, MCU 19 preservesinformation regarding the in-car system conjunction in RAM 13 asinformation regarding the video recording starting factor included inthe meta information (step S13).

After the video data starts being recorded, MCU 19 inputs a selectionstate of attribute selecting switch SW4 (step S14).

MCU 19 determines whether or not video recording is continuouslyperformed (step S15). For example, in a case where a video recordingstopping message is not acquired by communicator 21, the video recordingis continuously performed. In a case where the video recording is notcontinuously performed, MCU 19 finishes the attribute informationassigning operation.

If the video recording is continuously performed, MCU 19 determineswhether or not an input operation on attribute information assigningswitch SW3 is performed (step S16). In other words, attributeinformation is assigned through an operation performed by police officer7 during or after recording of video data. A selection state ofattribute selecting switch SW4 may be changed during recording of asingle video data item. In other words, a plurality of attributeinformation pieces may be assigned to a single video data item.

If there is an input operation on attribute information assigning switchSW3, MCU 19 reads attribute information corresponding to the state ofattribute selecting switch SW4 from EEPROM 16, and assigns the attributeinformation to the video data (step S17). If there is no input operationon attribute information assigning switch SW3, the flow proceeds to stepS13.

MCU 19 stores meta information including the assigned attributeinformation in storage 15 in association with video data recorded duringrecording or immediately before (step S18). The meta information hereincludes, for example, video position information, a camera ID, anofficer ID, attribute information (incident category), and a videorecording starting factor as shown in the recorded video list of FIG.12.

The video position information is acquired as current time from RTC 17during an input operation on attribute information assigning switch SW3,for example. The camera ID and the officer ID are acquired from EEPROM16, for example. The video recording starting factor is acquired fromRAM 13 in which the video recording starting factor is preserved in stepS13, for example. After the process in step S18 is performed, the flowproceeds to step S15.

In wearable camera 10, MCU 19 may light at least some of LEDs 26 a to 26c according to the preserved video recording starting factor. Forexample, according to the video recording starting factor, lighting timemay be changed, a blinking method may be changed, or a lighting colormay be changed.

Consequently, police officer 7 carrying wearable camera 10 can easilyrecognize starting of video recording and the video recording startingfactor without performing a voluntary operation by checking LEDs 26 a to26 c.

As mentioned above, according to the attribute information assigningoperation in wearable camera 10, attribute information can be easilyassigned immediately after recording or during recording, and thus metainformation can be preserved with respect to recorded video data.Therefore, for example, it is not necessary for police officer 7 toleave scene 8 imaged by wearable camera 10 and then to assign metainformation with in-station PC 71 or the like in police station 5 so asto edit the meta information. In other words, it is not necessary forpolice officer 7 to determine the type of video data while reproducingthe video data and to perform an input operation of attributeinformation or meta information, and it is possible to reduce time andeffort to input the attribute information or the meta information. Sincevideo data in which attribute information or meta information is notinput can be prevented from being collected, it is possible to minimizetime and effort to check individual video data, and thus to reduceefforts to determine the type of video data and to input the attributeinformation or the meta information.

Since wearable camera 10 holds the information regarding the videorecording starting factor included in the meta information, it can beunderstood after recording that wearable camera 10 has started videorecording in conjunction with in-car system 60 by using, for example,in-station PC 71, in-car PC 63, or a portable terminal.

As mentioned above, in the present exemplary embodiment, since wearablecamera 10 and in-car recorder 62 start video recording throughcooperation therebetween, the video recording can be started in responseto a video recording starting message from one of wearable camera 10 andin-car recorder 62 even in a case where the other of wearable camera 10and in-car recorder 62 does not start the video recording.

Therefore, for example, even in a case where police officer 7 hurriesfor an emergency response and thus forgets an input operation on videorecording switch SW1 of wearable camera 10 or cannot perform the inputoperation, wearable camera 10 can also start video recording if a videorecording starting trigger occurs in in-car recorder 62.

As mentioned above, according to wearable camera system 100, it ispossible to improve convenience of handling video data captured bywearable camera 10. It is possible to prevent video data from beingomitted for a specific period of time and thus to improve performance ofmonitoring scene 8 or evidence performance of the video data.

As mentioned above, wearable camera system 100 of the present exemplaryembodiment includes wearable camera 10 which can be mounted on a user,in-car recorder 62 which is equipped in a vehicle in which the userrides, and in-car camera 61 which is equipped in the vehicle. In-carcamera 61 includes a first capture which captures videos. In-carrecorder 62 includes a first communicator which performs communicationwith wearable camera 10 as a communication partner, and a first recorderwhich records first video data captured by in-car camera 61. Wearablecamera 10 includes a second capture which captures videos; a secondcommunicator which performs communication with in-car recorder 62 as acommunication partner; and a second recorder which records second videodata captured by the second capture. One of in-car recorder 62 andwearable camera 10 transmits video recording starting informationincluding information indicating that video recording has been startedto the other of in-car recorder 62 and wearable camera 10 when one ofin-car recorder 62 and wearable camera 10 starts the video recording.The other of in-car recorder 62 and wearable camera 10 starts videorecording after the video recording starting information is received.

The first communicator is, for example, wireless communicator 102 orwired communicator 103. The first recorder is, for example, CPU 101. Thesecond capture is, for example, capture 11. The second recorder is, forexample, MCU 19. The user is, for example, police officer 7. The vehicleis, for example, patrol car 6. The video recording starting informationis, for example, the video recording starting message.

Consequently, since wearable camera 10 and in-car recorder 62 startvideo recording through cooperation therebetween, one of wearable camera10 and in-car recorder 62 can assist the other thereof in the videorecording operation, and thus video data can be reliably recorded inboth of the devices. Therefore, wearable camera system 100 can improveconvenience of handling video data captured by wearable camera 10 andcan thus reduce recording omission of the video data. Thus, for example,it is possible to improve monitoring performance of wearable camerasystem 100 or evidence performance of video data.

In wearable camera system 100, one of in-car recorder 62 and wearablecamera 10 may transmit video recording stopping information includinginformation indicating that video recording has been stopped to theother of in-car recorder 62 and wearable camera 10 when one of in-carrecorder 62 and wearable camera 10 stops the video recording. The otherof in-car recorder 62 and wearable camera 10 may stop the videorecording after the video recording stopping information is received.The video recording stopping information is, for example, the videorecording stopping message.

Consequently, since wearable camera 10 and in-car recorder 62 stop videorecording through cooperation therebetween, one of wearable camera 10and in-car recorder 62 can assist the other thereof in the operation ofstopping the video recording, and thus recording of video data can bereliably stopped in both of the devices. Thus, wearable camera system100 can reduce recording omission of the video data and can reducerecording capacity required to record the video data.

In wearable camera system 100, wearable camera 10 may include anoperator, storage 15, and a controller. The operator receives anassigning operation of information associated with the second videodata. In a case where the assigning operation is received, storage 15stores factor information indicating a factor of starting of recordingof the second video data in correlation with the second video data. In acase where recording of the second video data is started on the basis ofthe video recording starting information, the controller storesconjunction information indicating that the video recording has beenstarted in conjunction with in-car recorder 62 in the factorinformation.

The operator is, for example, attribute information assigning switchSW3. The controller is, for example, MCU 19. The factor information is,for example, the information regarding the video recording startingfactor. The conjunction information is, for example, the informationregarding the in-car system conjunction.

Consequently, a user such as police officer 7 can identify information(meta information or the like) associated with video data, and caneasily recognize a factor which causes the video data to be recordedafter the video data is recorded by referring to the conjunctioninformation. Therefore, it is possible to facilitate management of videodata and thus to easily identify content of the video data after beingrecorded.

The video recording control method of the present exemplary embodimentis a video recording control method for wearable camera system 100including wearable camera 10 which can be mounted on a user, in-carrecorder 62 which is equipped in a vehicle in which the user rides, andin-car camera 61 which is equipped in the vehicle. The video recordingcontrol method includes an image capturing step of causing in-car camera61 to capture videos and causing wearable camera 10 to capture videos; avideo recording step of causing in-car recorder 62 to record first videodata captured by in-car camera 61 and causing wearable camera 10 torecord second video data captured by wearable camera 10; and acommunication step of performing communication between in-car recorder62 and wearable camera 10. In the video recording step, video recordingis started by one of in-car recorder 62 and wearable camera 10. In thecommunication step, video recording starting information includinginformation indicating that video recording has been started istransmitted to the other of in-car recorder 62 and wearable camera 10when one of in-car recorder 62 and wearable camera 10 starts the videorecording. In the video recording step, video recording is started afterthe other of in-car recorder 62 and wearable camera 10 receives thevideo recording starting information.

Consequently, since wearable camera 10 and in-car recorder 62 startvideo recording through cooperation therebetween, one of wearable camera10 and in-car recorder 62 can assist the other thereof in the videorecording operation, and thus video data can be reliably recorded inboth of the devices. Thus, wearable camera system 100 can improveconvenience of handling video data captured by wearable camera 10 andcan thus reduce recording omission of the video data. Therefore, forexample, it is possible to improve monitoring performance of wearablecamera system 100 or evidence performance of video data.

Next, a second exemplary embodiment of the present invention will bedescribed. A configuration related to the second exemplary embodiment isthe same as the configuration described with reference to FIGS. 1 to 13.An operation mode of wearable camera system 100 of the second exemplaryembodiment will be described.

Operation modes are defined according to the operation policy of eachpolice station 5, and are set by in-station PC 71 executing managementsoftware 70. The operation modes include an officer mode and a car mode.

Setting information of the operation modes is transmitted fromin-station PC 71 to in-car recorder 62 so as to be held in flash ROM 104or the like of in-car recorder 62, and is transmitted from in-station PC71 to wearable camera 10 so as to be held in EEPROM 16 or the like ofwearable camera 10.

The officer mode is employed in an operation in which combinations ofpolice officer 7 and patrol car 6 in which police officer 7 rides differfor every dispatch, and is set by in-station PC 71. The car mode isemployed in an operation in which combinations of police officer 7 andpatrol car 6 in which police officer 7 rides are the same as each otherfor every dispatch, and is set by in-station PC 71. The operation modesare defined according to the operation policy of police station 5, andthus a frequency thereof to be changed is low.

In the officer mode, combinations of police officer 7 and patrol car 6are changed every time, and thus police officer 7 cannot be identifiedeven using the car ID. For this reason, in the officer mode, at leastthe officer ID is set in EEPROM 16 or the like of wearable camera 10 andflash ROM 104 or the like of in-car recorder 62 through setting andregistration using in-station PC 71 or login to in-car PC 63 when policeofficer 7 is dispatched from police station 5.

Consequently, since the officer ID held in in-car recorder 62 iscollated with the officer ID held in wearable camera 10, both of policeofficer 7 and patrol car 6 used by police officer 7 can be identified.

In a case where the same police officer 7 uses the same wearable camera10 for every dispatch, in-station PC 71 may set and registeridentification information (officer ID) of a user of wearable camera 10once for the first time.

In the car mode, since combinations of police officer 7 and patrol car 6are not changed, the car ID corresponds to the officer ID, and policeofficer 7 can be identified by using the car ID. For this reason, in thecar mode, at least car ID is set in EEPROM 16 or the like of wearablecamera 10 and flash ROM 104 or the like of in-car recorder 62 throughsetting and registration using in-station PC 71 or login to in-car PC 63when police officer 7 is dispatched from police station 5.

Consequently, since the car ID held in in-car recorder 62 is collatedwith the car ID held in wearable camera 10, both of police officer 7 andpatrol car 6 used by police officer 7 can be identified.

In a case where the same police officer 7 uses the same patrol car 6 forevery dispatch, in-station PC 71 may set and register identificationinformation (car ID) of patrol car 6 used by police officer 7 once forthe first time.

Next, a description will be made of an operation example of wearablecamera system 100. Also in the second exemplary embodiment, the sameconfiguration as described above will be given the same referencenumeral and will be described.

FIG. 17 is a flowchart illustrating an operation example in a case wherein-car recorder 62 searches for specific wearable camera 10 as acommunication partner. Here, a communication partner is detected byusing, for example, wireless LAN communication, but a communicationpartner may be detected by using other methods.

When police officer 7 is dispatched, it is expected that a plurality ofpolice officers 7 ride in patrol car 6, and each police officer 7carries wearable camera 10. Also in this case, in-car recorder 62 canspecify wearable camera 10 which is a wireless connection target among aplurality of wearable cameras 10 through the process illustrated in FIG.14. In-car recorder 62 may be specified as in-car recorder 62 which is awireless connection target by authenticating whether or not detectedsingle wearable camera 10 is a wearable camera to be wirelesslyconnected.

First, wireless communicator 102 detects at least one wearable camera 10on the wireless network (step S11). Wearable camera 10 is also referredto as a “WCAM”.

CPU 101 collates detected wearable cameras 10 by using, for example, anSSID and a password (encryption key) so as to determine whether or noteach camera is wearable camera 10 which can be wirelessly connected(step S12). If the camera is wearable camera 10 which cannot bewirelessly connected, the flow proceeds to step S11.

If the camera is wearable camera 10 which can be wirelessly connected,CPU 101 refers to the operation mode of wearable camera system 100 whichare held and set in, for example, flash ROM 104 in advance, anddetermines whether the operation mode is the officer mode or the carmode (step S13).

In step S13, if the operation mode of wearable camera system 100 is theofficer mode, wireless communicator 102 acquires an officer ID fromwearable camera 10 (step S14).

CPU 101 determines whether or not the officer ID held in flash ROM 104or the like matches the officer ID acquired from wearable camera 10(step S15). If both of the two IDs do not match each other, the flowproceeds to step S11.

If the officer IDs match each other, CPU 101 specifies detected wearablecamera 10 as wearable camera 10 which is a communication partner (stepS16). Wireless communicator 102 establishes a communication link betweenin-car recorder 62 and specified wearable camera 10.

If the operation mode of wearable camera system 100 is the car mode instep S13, wireless communicator 102 acquires a car ID from wearablecamera 10 (step S17).

CPU 101 determines whether or not the car ID held in flash ROM 104 orthe like matches the car ID acquired from wearable camera 10 (step S18).If both of the two IDs do not match each other, the flow proceeds tostep S11.

If the car IDs match each other, CPU 101 specifies detected wearablecamera 10 as wearable camera 10 which is a communication partner (stepS19). Wireless communicator 102 establishes a communication link betweenin-car recorder 62 and specified wearable camera 10.

If a communication partner is derived in step S16 or S19, CPU 101generates management table T1 illustrated in FIG. 18.

FIG. 18 is a schematic diagram illustrating an example of managementtable T1 which holds information regarding wearable camera 10 derived asa communication partner (pair). Management table T1 holds identificationinformation or a name of wearable camera 10 (WCAM), an IP address foraccessing wearable camera 10, and information (Yes/No) indicatingwhether or not wearable camera 10 is selected as a communicationpartner. In a case where wearable camera 10 is selected as acommunication partner, “Yes” is set, and in a case where wearable camera10 is not selected as a communication partner, “No” is set. Theinformation regarding wearable camera 10 detected in step S11 is held inmanagement table T1.

Management table T1 exemplifies that WCAM-2 is specified as wearablecamera 10 which is a communication partner among a plurality of wearablecameras 10 (WCAM-1, WCAM-2, WCAM-5, WCAM-8, and WCAM-12) (refer to FIGS.18 and 20).

According to the process illustrated in FIG. 17, it is possible tosearch for in-car recorder 62 and specific wearable camera 10 betweenwhich a communication link should be established, by usingidentification information which is appropriate for an operation ofpolice station 5. Also in this case, police officer 7, patrol car 6 usedby police officer 7, and wearable camera 10 can be linked to each other.

CPU 101 may specify detected wearable camera 10 as a communicationpartner through collation using an SSID and a password when singlewearable camera 10 is detected. In other words, the processes in stepS13 and the subsequent steps may be omitted.

FIG. 19 is a flowchart illustrating an operation example in a case wherewearable camera 10 searches for in-car recorder 62 as a communicationpartner. Here, a communication partner is detected by using, forexample, wireless LAN communication, but a communication partner may bedetected by using other methods.

When police officer 7 is dispatched, since single in-car recorder 62 isprovided in patrol car 6 in most cases, wearable camera 10 can specifyin-car recorder 62 which is a wireless connection target byauthenticating whether or not detected single in-car recorder 62 isin-car recorder 62 which is to be wirelessly connected. It is alsoexpected that a plurality of in-car recorders 62 may be provided inpatrol car 6 or a plurality of patrol cars 6 are collected at scene 8.In this case, wearable camera 10 may specify in-car recorder 62 which isa wireless connection target among a plurality of in-car recorders 62.

First, communicator 21 detects in-car recorder 62 on the wirelessnetwork (step S21).

MCU 19 collates detected in-car recorder 62 by using, for example, anSSID and a password (encryption key) so as to determine whether or notin-car recorder 62 is in-car recorder 62 which can be wirelesslyconnected (step S22). If the detected in-car recorder 62 is in-carrecorder 62 which cannot be wirelessly connected, the flow proceeds tostep S21.

If the detected in-car recorder 62 is in-car recorder 62 which can bewirelessly connected, MCU 19 refers to the operation mode of wearablecamera system 100 which are held and set in, for example, EEPROM 16 inadvance, and determines whether the operation mode is the officer modeor the car mode (step S23).

In step S23, if the operation mode of wearable camera system 100 is theofficer mode, communicator 21 acquires an officer ID from in-carrecorder 62 (step S24).

MCU 19 determines whether or not the officer ID held in EEPROM 16 or thelike matches the officer ID acquired from in-car recorder 62 (step S25).If both of the two IDs do not match each other, the flow proceeds tostep S21.

If the officer IDs match each other, MCU 19 specifies detected in-carrecorder 62 as in-car recorder 62 which is a communication partner (stepS26). Communicator 21 establishes a communication link between specifiedin-car recorder 62 and wearable camera 10.

If the operation mode of wearable camera system 100 is the car mode instep S23, communicator 21 acquires a car ID from in-car recorder 62(step S27).

MCU 19 determines whether or not the car ID held in EEPROM 16 or thelike matches the car ID acquired from in-car recorder 62 (step S28). Ifboth of the two IDs do not match each other, the flow proceeds to stepS21.

If the car ID held in EEPROM 16 or the like matches the car ID acquiredfrom in-car recorder 62, MCU 19 specifies detected in-car recorder 62 asin-car recorder 62 which is a communication partner (step S29).Communicator 21 establishes a communication link between specifiedin-car recorder 62 and wearable camera 10.

If a communication partner is derived in step S26 or S29, MCU 19generates a management table such as management table T1 illustrated inFIG. 18. The management table holds identification information or a nameof in-car recorder 62, an IP address for accessing in-car recorder 62,and information (Yes/No) indicating whether or not in-car recorder 62 isselected as a communication partner. The information regarding in-carrecorder 62 detected in step S21 is held in the management table.

According to the process illustrated in FIG. 19, it is possible tosearch for specific in-car recorder 62 and wearable camera 10 betweenwhich a communication link should be established, by usingidentification information which is appropriate for an operation ofpolice station 5. Also in this case, police officer 7, patrol car 6 usedby police officer 7, and wearable camera 10 can be linked to each other.

MCU 19 may specify detected in-car recorder 62 as a communicationpartner through collation using an SSID and a password when singlein-car recorder 62 is detected. In other words, the processes in stepS23 and the subsequent steps may be omitted.

FIG. 20 is a sequence diagram illustrating an operation example ofwearable camera system 100 in a case where wearable camera 10 startsvideo recording through in-car system conjunction.

FIG. 20 exemplifies that in-car recorder 62 and wearable camera 10 areconnected to each other in a wireless manner via the wireless LAN, butthe recorder and the camera may be connected to each other in a wirelessmanner according to other methods, and may be connected to each other ina wired manner.

In in-car recorder 62, if a video recording starting trigger isdetected, CPU 101 starts recording of video data which is captured byin-car camera 61 and starts storing of the video data in SSD 111 (stepS31).

The video recording starting trigger in in-car recorder 62 includes, forexample, detection of pressing of buttons 109, detection of starting oflighting and ringing of patrol lamps of patrol car 6 in CPU 101,detection of a traveling speed of patrol car 6 being equal to or higherthan a predetermined speed (for example, 100 km/h) in the speed sensor,detection of an impact in the acceleration sensor (that is, detection ofa change in acceleration of a predetermined threshold value or greater),and detection of being out of a communication range in whichcommunication between wireless communicator 102 and wearable camera 10cannot be performed.

CPU 101 refers to management table T1 indicating the results of theabove-described searching process of a communication partner whenrecording of the video data is started, and acquires informationregarding wearable camera 10 as a communication partner (step S32). Theacquired information regarding wearable camera 10 includes at least someof the information regarding wearable camera 10 held in management tableT1.

Wireless communicator 102 notifies wearable camera 10 regarding whichthe information is acquired, that is, specific wearable camera 10 (forexample, WCAM-2) of a video recording starting message (for example, amessage “REC START”) including information indicating that the videorecording has been started (step S33).

In specific wearable camera 10 (for example, WCAM-2), if communicator 21receives the video recording starting message from in-car recorder 62,MCU 19 starts recording of video data which is captured by capture 11and starts storing of the video data in storage 15 (step S34).

As mentioned above, video recording is started in specific wearablecamera 10 in conjunction with video recording starting in in-carrecorder 62. Thus, for example, even in a case where police officer 7forgets a video recording starting operation on video recording switchSW1 or snapshot switch SW2 of specific wearable camera 10 due toemergency response, video data of scene 8 can be recorded and be checkedin the future.

For example, in a case where in-car recorder 62 and wearable camera 10have a long distance therebetween and are thus out of a communicationrange using the wireless LAN when specific wearable camera 10 as acommunication partner is derived, in-car recorder 62 may transmit avideo recording starting message after the wireless connection isrecovered.

Specific wearable camera 10 may not start video recording immediatelyafter receiving the video recording starting message. For example,specific wearable camera 10 may not start video recording when the videorecording starting message is received during traveling of patrol car 6,and may start video recording when detecting that the wirelessconnection with in-car recorder 62 is canceled due to becoming distantfrom patrol car 6. Consequently, it is possible to use a resource ofstorage 15 which accumulates recorded video data, with high efficiency.

FIG. 21 is a sequence diagram illustrating an operation example ofwearable camera system 100 in a case where in-car recorder 62 startsvideo recording through WCAM conjunction.

FIG. 21 exemplifies that in-car recorder 62 and wearable camera 10 areconnected to each other in a wireless manner via the wireless LAN, butthe recorder and the camera may be connected to each other in a wirelessmanner according to other methods, and may be connected to each other ina wired manner.

In wearable camera 10, if a video recording starting trigger isdetected, MCU 19 starts recording of video data which is captured bycapture 11 and starts storing of the video data in storage 15 (stepS41).

The video recording starting trigger in wearable camera 10 includes, forexample, detection of pressing of video recording switch SW1 or snapshotswitch SW2 in MCU 19, detection of cancelation of wireless connectionbetween in-car recorder 62 and wearable camera 10 in communicator 21,detection of an impact in the acceleration sensor (that is, detection ofa change in acceleration of a predetermined threshold value or greater),detection of police officer 7 being present in a predetermined area inGPS 18, and detection of police officer 7 starting to run in GPS 18. Thedetection of an impact in the acceleration sensor includes detection ofpolice officer 7 starting to run and falling.

MCU 19 refers to the management table indicating the results of theabove-described searching process of a communication partner whenrecording of the video data is started, and acquires informationregarding in-car recorder 62 as a communication partner (step S42). Theacquired information regarding in-car recorder 62 includes at least someof the information regarding in-car recorder 62 held in the managementtable.

Communicator 21 notifies in-car recorder 62 regarding which theinformation has been acquired, that is, specific in-car recorder 62 of avideo recording starting message (for example, a message “REC START”)including information indicating that video recording has been started(step S43).

In specific in-car recorder 62, if wireless communicator 102 receivesthe video recording starting message from wearable camera 10, CPU 101starts recording of video data which is captured by in-car camera 61 andstarts storing of the video data in SSD 111 (step S44).

As mentioned above, video recording is started in specific in-carrecorder 62 in conjunction with video recording starting in wearablecamera 10. Thus, for example, even in a case where police officer 7forgets a video recording starting operation on buttons 109 in patrolcar 6, video data of scene 8 can be recorded and be checked in thefuture.

As mentioned above, in the present exemplary embodiment, a cooperatingcommunication partner for starting video recording can be derived byusing, for example, a small amount of information (for example, anofficer ID or a car ID) in accordance with the way of using patrol car 6or wearable camera 10 according to the operation of police station 5.Therefore, it is possible to save time and effort to derive acommunication partner.

Since video recording is started through cooperation between wearablecamera 10 and in-car recorder 62, the video recording can be started inresponse to a video recording starting message from one of wearablecamera 10 and in-car recorder 62 even in a case where the other ofwearable camera 10 and in-car recorder 62 does not start the videorecording.

Therefore, for example, even in a case where police officer 7 hurriesfor an emergency response and thus forgets an input operation on videorecording switch SW1 of wearable camera 10 or cannot perform the inputoperation, wearable camera 10 can also start video recording if a videorecording starting trigger occurs in in-car recorder 62.

As mentioned above, according to wearable camera system 100, it ispossible to improve convenience of handling video data captured bywearable camera 10. It is possible to prevent video data from beingomitted for a specific period of time and thus to improve performance ofmonitoring scene 8 or evidence performance of the video data.

As mentioned above, wearable camera system 100 of the present exemplaryembodiment includes wearable camera 10 which can be mounted on a user,in-car recorder 62 which is equipped in a vehicle in which the userrides, and in-car camera 61 which is equipped in the vehicle. In-carcamera 61 includes a first capture which captures videos. In-carrecorder 62 includes a first deriver which derives specific wearablecamera 10 as a cooperating communication partner for recording videodata from a plurality of wearable cameras 10 on the basis of anoperation mode of wearable camera system 100; a first communicator whichperforms communication with specific wearable camera 10; and a firstrecorder which records first video data captured by in-car camera 61.Wearable camera 10 includes a second capture which captures videos; asecond communicator which performs communication with an in-car recorderas a communication partner; and a second recorder which records secondvideo data captured by the second capture.

The first deriver is, for example, CPU 101. The first communicator is,for example, wireless communicator 102 or wired communicator 103. Thefirst recorder is, for example, CPU 101. The second capture is, forexample, capture 11. The second communicator is, for example,communicator 21. The second recorder is, for example, MCU 19. The useris, for example, police officer 7. The vehicle is, for example, patrolcar 6.

Consequently, it is possible to select a communication partner forrecording video data through cooperation between wearable camera 10 andin-car recorder 62 on the basis of an operation mode (for example, anoperation reference of wearable camera system 100). Therefore, sincespecific wearable camera 10 and in-car recorder 62 start video recordingthrough cooperation therebetween, one of wearable camera 10 and in-carrecorder 62 can assist the other thereof in the video recordingoperation, and thus video data can be reliably recorded in both of thedevices. Thus, wearable camera system 100 can improve convenience ofhandling video data captured by wearable camera 10 and can thus reducerecording omission of the video data. For example, it is possible toprevent video data from being omitted for a specific period of time andthus to improve performance of monitoring scene 8 or evidenceperformance of the video data.

In wearable camera system 100, in a case where a first operation mode inwhich identification information regarding the user is held in in-carrecorder 62 is set as the operation mode, in-car recorder 62 may receiveidentification information regarding the user from wearable camera 10.In a case where the identification information regarding the userreceived from wearable camera 10 matches the identification informationregarding the user held in in-car recorder 62, in-car recorder 62 mayderive a wearable camera which holds the matching identificationinformation regarding the user as specific wearable camera 10.

The first operation mode is, for example, an officer mode. Theidentification information regarding the user is, for example, anofficer ID.

For example, in an operation (first operation mode) in which acombination of a user and a vehicle is frequently changed, at leastinformation for identifying the user is stored in wearable camera 10.Also in this case, it is possible to understand matching between thevehicle and the user using wearable camera 10 by using theidentification information regarding the user and thus to set acommunication partner by linking in-car recorder 62 equipped in thevehicle used by the user to wearable camera 10.

In wearable camera system 100, in a case where a second operation modein which identification information regarding the vehicle is held inin-car recorder 62 is set as the operation mode, in-car recorder 62 mayreceive identification information regarding the vehicle from wearablecamera 10. In a case where the identification information regarding thevehicle received from wearable camera 10 matches the identificationinformation regarding the vehicle held in in-car recorder 62, in-carrecorder 62 may derive wearable camera 10 which holds the matchingidentification information regarding the vehicle as specific wearablecamera 10.

The second operation mode is, for example, a car mode. Theidentification information for the vehicle, for example, a car ID.

For example, in an operation (second operation mode) in which acombination of a user and a vehicle is not greatly changed, at leastinformation for identifying the vehicle is stored in wearable camera 10.Also in this case, it is possible to understand matching between thevehicle and the user using wearable camera 10 by using theidentification information regarding the vehicle and thus to set acommunication partner by linking in-car recorder 62 equipped in thevehicle used by the user to wearable camera 10.

In wearable camera system 100, in-car recorder 62 may start recording ofthe first video data, and may transmit video recording startinginformation including information indicating that video recording hasbeen started to specific wearable camera 10. Specific wearable camera 10may start recording of the second video data after receiving the videorecording starting information.

Consequently, since specific wearable camera 10 and in-car recorder 62can start video recording through cooperation therebetween, one ofwearable camera 10 and in-car recorder 62 can assist the other thereofin the video recording operation, and thus video data can be reliablyrecorded in both of the devices. Thus, wearable camera system 100 canimprove convenience of handling video data captured by wearable camera10 and can thus reduce recording omission of the video data. Forexample, it is possible to prevent video data from being omitted for aspecific period of time and thus to improve performance of monitoringscene 8 or evidence performance of the video data.

Wearable camera system 100 of the present exemplary embodiment includeswearable camera 10 which can be mounted on a user, in-car recorder 62which is equipped in a vehicle in which the user rides, and in-carcamera 61 which is equipped in the vehicle. In-car camera 61 includes afirst capture which captures videos. In-car recorder 62 includes a firstcommunicator which performs communication with wearable camera 10, and afirst recorder which records first video data captured by in-car camera61. Wearable camera 10 includes a second capture which captures videos;a second deriver which derives specific in-car recorder 62 as acommunication partner working in conjunction for recording video datafrom a plurality of in-car recorders 62 on the basis of an operationmode of wearable camera system 100; a second communicator which performscommunication with specific in-car recorder 62; and a second recorderwhich records video data captured by the second capture. Second deriveris, for example, MCU 19.

Consequently, it is possible to select a communication partner forrecording video data through cooperation between wearable camera 10 andin-car recorder 62 on the basis of an operation mode (for example, anoperation reference of wearable camera system 100). Therefore, sincewearable camera 10 and specific in-car recorder 62 start video recordingthrough cooperation therebetween, one of wearable camera 10 and specificin-car recorder 62 can assist the other thereof in the video recordingoperation, and thus video data can be reliably recorded in both of thedevices. Thus, wearable camera system 100 can improve convenience ofhandling video data captured by wearable camera 10 and can thus reducerecording omission of the video data. For example, it is possible toprevent video data from being omitted for a specific period of time andthus to improve performance of monitoring scene 8 or evidenceperformance of the video data.

In wearable camera system 100, in a case where a third operation mode inwhich identification information regarding the user is held in wearablecamera 10 is set as the operation mode, wearable camera 10 receivesidentification information regarding the user from in-car recorder 62,and, when the identification information regarding the user receivedfrom in-car recorder 62 matches the identification information regardingthe user held in wearable camera 10, wearable camera 10 may derivein-car recorder 62 which holds the matching identification informationregarding the user as specific in-car recorder 62. The third operationmode is, for example, an officer mode.

Consequently, for example, in an operation (third operation mode) inwhich a combination of a user and a vehicle is frequently changed, atleast information for identifying the user is stored in wearable camera10. Also in this case, it is possible to understand matching between thevehicle and the user using wearable camera 10 by using theidentification information regarding the user and thus to set acommunication partner by linking in-car recorder 62 equipped in thevehicle used by the user to wearable camera 10. In wearable camerasystem 100, in a case where a fourth operation mode in whichidentification information regarding the vehicle is held in wearablecamera 10 is set as the operation mode, wearable camera 10 may receiveidentification information regarding the vehicle from in-car recorder62. In a case where the identification information regarding the vehiclereceived from in-car recorder 62 matches the identification informationregarding the vehicle held in wearable camera 10, in-car recorder 62which holds the matching identification information regarding thevehicle may be derived as specific in-car recorder 62. The fourthoperation mode is, for example, a car mode.

For example, in an operation (fourth operation mode) in which acombination of a user and a vehicle is not greatly changed, at leastinformation for identifying the vehicle is stored in wearable camera 10.Also in this case, it is possible to understand matching between thevehicle and the user using wearable camera 10 by using theidentification information regarding the vehicle and thus to set acommunication partner by linking in-car recorder 62 equipped in thevehicle used by the user to wearable camera 10.

In wearable camera system 100, wearable camera 10 may start recording ofthe second video data, and may transmit video recording startinginformation including information indicating that video recording hasbeen started to specific in-car recorder 62. Specific in-car recorder 62may start recording of the first video data after receiving the videorecording starting information.

Consequently, since wearable camera 10 and specific in-car recorder 62can start video recording through cooperation therebetween, one ofwearable camera 10 and specific in-car recorder 62 can assist the otherthereof in the video recording operation, and thus video data can bereliably recorded in both of the devices. Thus, wearable camera system100 can improve convenience of handling video data captured by wearablecamera 10 and can thus reduce recording omission of the video data. Forexample, it is possible to prevent video data from being omitted for aspecific period of time and thus to improve performance of monitoringscene 8 or evidence performance of the video data.

The video recording control method of the present exemplary embodimentis a video recording control method for wearable camera system 100including wearable camera 10 which can be mounted on a user, in-carrecorder 62 which is equipped in a vehicle in which the user rides, andin-car camera 61 which is equipped in the vehicle. The video recordingcontrol method includes a step of causing in-car camera 61 to capturevideos; a step of causing wearable camera 10 to capture videos; a stepof causing in-car recorder 62 to derive specific wearable camera 10 as acommunication partner working in conjunction for recording video datafrom a plurality of wearable cameras 10 on the basis of an operationmode of wearable camera system 100; a step of causing in-car recorder 62to start recording of first video data captured by in-car camera 61; astep of transmitting video recording starting information includinginformation indicating that video recording has been started by in-carrecorder 62 to specific wearable camera 10; and a step of causingspecific wearable camera 10 to start recording of second video datacaptured by specific wearable camera 10 after receiving the videorecording starting information.

Consequently, it is possible to select a communication partner forrecording video data through cooperation between wearable camera 10 andin-car recorder 62 on the basis of an operation mode (for example, anoperation reference of wearable camera system 100). Therefore, sincespecific wearable camera 10 and in-car recorder 62 start video recordingthrough cooperation therebetween, one of wearable camera 10 and in-carrecorder 62 can assist the other thereof in the video recordingoperation, and thus video data can be reliably recorded in both of thedevices. Thus, wearable camera system 100 can improve convenience ofhandling video data captured by wearable camera 10 and can thus reducerecording omission of the video data. For example, it is possible toprevent video data from being omitted for a specific period of time andthus to improve performance of monitoring scene 8 or evidenceperformance of the video data.

The video recording control method of the present exemplary embodimentis a video recording control method for a wearable camera systemincluding a wearable camera which can be mounted on a user, in-carrecorder 62 which is equipped in a vehicle in which the user rides, andin-car camera 61 which is equipped in the vehicle. The video recordingcontrol method includes a step of causing in-car camera 61 to capturevideos; a step of causing wearable camera 10 to capture videos; a stepof causing wearable camera 10 to derive specific in-car recorder 62 as acommunication partner working in conjunction for recording video datafrom a plurality of in-car recorders 62 on the basis of an operationmode of wearable camera system 100; a step of causing wearable camera 10to start recording of second video data captured by wearable camera 10;a step of transmitting video recording starting information includinginformation indicating that video recording has been started by wearablecamera 10 to specific in-car recorder 62; and a step of causing specificin-car recorder 62 to start recording of first video data captured byin-car camera 61 after receiving the video recording startinginformation.

Consequently, it is possible to select a communication partner forrecording video data through cooperation between wearable camera 10 andin-car recorder 62 on the basis of an operation mode (for example, anoperation reference of wearable camera system 100). Therefore, sincewearable camera 10 and specific in-car recorder 62 start video recordingthrough cooperation therebetween, one of wearable camera 10 and specificin-car recorder 62 can assist the other thereof in the video recordingoperation, and thus video data can be reliably recorded in both of thedevices. Thus, wearable camera system 100 can improve convenience ofhandling video data captured by wearable camera 10 and can thus reducerecording omission of the video data. For example, it is possible toprevent video data from being omitted for a specific period of time andthus to improve performance of monitoring scene 8 or evidenceperformance of the video data.

Next, a third exemplary embodiment of the present invention will bedescribed. A configuration related to the third exemplary embodiment isthe same as the configuration described with reference to FIGS. 1 to 9.First, a description will be made of assignment of attribute informationto video data.

In wearable camera system 100, a case is assumed in which video datarecorded by wearable camera 10 is transmitted to and accumulated inservers SV1 to SV3, and is used. Similarly, a case is assumed in whichvideo data captured by in-car camera 61 is recorded by in-car recorder62 so as to be transmitted to and accumulated in servers SV1 to SV3, andis used.

In this case, for example, in-station PC 71 can extract and reproducetarget video data from the accumulated items of video data in responseto an operation performed by a police officer in police station 5 on thebasis of some sort of attribute information associated with video data,such as the type of video content, police officer 7 which has performedimage capturing, the date and time, and an image capturing location. Atthis time, attribute information correlated with the video data is used.As a result of the attribute information being assigned to the videodata, it is easy to discriminate captured videos from each other, andthus it becomes easier to extract target video data.

Here, wearable camera 10 assigns classification information (Classify)indicating the type of video content as the attribute information, andthe video data items can be individually sorted by the type. Theclassification information indicates an incident category regardingcontent of the video data. Assignment of the attribute information tothe video data is also referred to as tagging or the like. The attributeinformation is not limited to the classification information, andincludes all types of information regarding recorded video data. Theclassification information, which is the attribute information, may bearranged in hierarchical structure, or may be categorized in multiplesystems differently classified.

As mentioned above, in-car recorder 62 assigns classificationinformation (Classify) indicating the type of video content as theattribute information, and the video data items can be individuallysorted by the type.

FIG. 22 is a schematic diagram illustrating an example of attributeinformation in wearable camera 10. The attribute information is selectedby operating attribute selecting switch SW4, and is assigned byoperating attribute information assigning switch SW3.

In a case of using wearable camera 10, as illustrated in FIG. 22, theattribute information is allocated and is set so as to respectivelycorrespond to states (contact point positions) C1 to C3 of attributeselecting switch SW4. In the illustrated example, a case is assumed inwhich police officer 7 captures images of scene 8 (for example, anincident scene). Driving under the influence is allocated to C1; drugabuse violations are allocated to C2; and stolen property is allocatedto C3.

In the allocation of the attribute information, for example, MCU 19 ofwearable camera 10 selects and sets attribute information which isfrequently used by police officer 7 among a plurality of definedattribute information pieces. The set content of attribute informationis, for example, stored in EEPROM 16 of wearable camera 10 as one ofsetting information pieces.

FIG. 23 is a schematic diagram illustrating an example of attributeinformation in in-car recorder 62. In in-car recorder 62, for example,communicator 203 acquires attribute information which is input via input205 of in-car PC 63, and CPU 101 assigns the acquired attributeinformation to video data captured by in-car camera 61 and stores theattribute information in SSD 111 in association with the video data. Inthe assignment of the attribute information using in-car recorder 62,the number of contact points is not fixed unlike in attribute selectingswitch SW4, and thus more types of attribute information can beassigned. The attribute information is stored in association with thevideo data alone or as meta information including the attributeinformation.

As illustrated in FIG. 23, police officer 7 can input any one of, forexample, eleven attribute information pieces via in-car PC 63. Theattribute information includes, for example, information regardingdisorderly conduct, driving under the influence, drunkenness, drug abuseviolations, liquor law violations, Peeping Tom, trespass of realproperty, stolen property, vandalism, weapons, and all other offenses.

Therefore, police officer 7 can assign attribute information which ismore detailed than the attribute information used by wearable camera 10,to video data captured by, for example, in-car camera 61, and can thusassign attribute information which is more appropriate for a situationof actual scene 8.

FIG. 24 is a schematic diagram illustrating an example of a datastructure of video recording data. The video recording data includesrecorded video data and meta information corresponding to the videodata. The meta information includes attribute information as will bedescribed later. Video recording data which is captured and recorded bywearable camera 10 has the same format as that of video recording datawhich is captured by in-car camera 61 and is recorded by in-car recorder62.

Next, a description will be made of a data structure of a recorded videolist. A recorded video list associated with video data captured bywearable camera 10 is held in storage 15 of wearable camera 10. Arecorded video list associated with video data captured by in-car camera61 is held in SSD 111 of in-car recorder 62.

FIG. 25 is a schematic diagram illustrating an example of a datastructure of the recorded video list held in wearable camera 10.

If an input operation on attribute information assigning switch SW3 isdetected during video recording or after video recording, wearablecamera 10 generates attribute information associated with video data ofa video recording target and stores meta information including theattribute information in storage 15. In other words, video recordingdata stored in storage 15 includes the video data and the metainformation. In a case where the video data is transmitted to serversSV1 to SV3, wearable camera 10 transmits and accumulates the videorecording data including the video data and the meta information to andin servers SV1 to SV3. The video data and the meta information may betransmitted separately from each other.

The meta information associated with the video data is stored in a formof the recorded video list as illustrated in FIG. 25, for example. Themeta information of the recorded video list includes video positioninformation (video time information), a car ID, an officer ID, attributeinformation (incident category), a video recording starting factor, andother information.

The video data and the meta information are linked to each other byusing a video data ID. The video data ID is identification informationfor identifying recorded video data. The video data ID is assigned tothe video data, for example, at the time of starting video recording,during the video recording, or at the time of completing the videorecording. The video data ID includes, for example, recording start timeof the video data, a file name, and other IDs.

The video position information is information regarding time at whichthe meta information is assigned to the video data, that is, informationregarding time (also referred to as attribute information assigningtime) at which an input operation on attribute information assigningswitch SW3 is detected.

The car ID is identification information for identifying individualpatrol car 6. The officer ID is identification information foridentifying police officer 7 using wearable camera 10. By setting thecar ID and the officer ID, it is possible to discriminate which policeofficer 7 using which patrol car 6 has recorded the video data by usingwearable camera 10.

The incident category is classification information for identifying thetype of video data, and is assigned in accordance with attributeselecting switch SW4 on the basis of the set content of the attributeinformation illustrated in FIG. 10.

The video recording starting factor indicates a factor which causesrecording of the video data to be started. The video recording startingfactor includes, for example, detection of pressing of video recordingswitch SW1 or snapshot switch SW2, detection of a video recordingstarting trigger based on information from the sensor (for example, anacceleration sensor), RTC 17, or GPS 18 provided in wearable camera 10,and in-car system conjunction.

The in-car system conjunction indicates that wearable camera 10 startsvideo recording in response to a video recording starting instructionfrom in-car recorder 62 through cooperation between in-car system 60 andwearable camera 10.

The other information includes, for example, GPS information. The GPSinformation is position information indicating a location where thevideo data was recorded, and, for example, current position informationat the time of assigning the attribute information is acquired from GPS18 and is assigned as the GPS information.

The meta information assigned by wearable camera 10 is assigned throughprocessing in MCU 19, for example, and is stored in storage 15 inassociation with the video data captured by wearable camera 10.

One or more meta information pieces may be assigned to a single videodata item, that is, a single video data ID. For example, in a case wherepolice officer 7 observes the scene of drug abuse violations during acrackdown on driving under the influence, police officer 7 performs aninput operation on attribute information assigning switch SW3 more thantwice while continuing to record video data, and thus wearable camera 10can assign two or more meta information pieces to a single video dataitem.

FIG. 26 is a schematic diagram illustrating an example of a datastructure of the recorded video list held in in-car recorder 62.

The recorded video list held in in-car recorder 62 also includes metainformation including attribute information associated with video data.The content of the meta information is the same as the content of themeta information illustrated in FIG. 25. However, in-car recorder 62 canassign more types of attribute information (incident category) thanattribute information assigned by wearable camera 10. The attributeinformation in in-car recorder 62 is input via, for example, input 205of in-car PC 63 and is acquired from in-car PC 63. In in-car recorder62, the video recording starting factor includes detection of pressingof the attribute information assigning button, detection of a videorecording starting trigger based on information from the sensors (forexample, a speed sensor, an acceleration sensor, and a dooropening/closing sensor) provided in in-car system 60, RTC 17, or GPS107, and WCAM conjunction.

The WCAM conjunction indicates that in-car camera 61 has started videorecording under the instruction of in-car recorder 62 in response to avideo recording starting instruction from wearable camera 10 throughcooperation between in-car system 60 and wearable camera 10.

The meta information assigned by in-car recorder 62 is assigned throughprocessing in CPU 101, for example, and is stored in SSD 111 inassociation with the video data captured by in-car camera 61.

Next, operation examples of wearable camera system 100 will bedescribed.

FIG. 27 is a sequence diagram illustrating a first example of anattribute information assigning procedure in wearable camera system 100.In FIG. 27, a case is assumed in which wearable camera 10 starts videorecording earlier than in-car recorder 62 and assigns attributeinformation earlier than in-car recorder 62.

FIG. 27 exemplifies that in-car recorder 62 and wearable camera 10 areconnected to each other in a wireless manner via the wireless LAN, butthe recorder and the camera may be connected to each other in a wirelessmanner according to other methods, and may be connected to each other ina wired manner.

First, in-car recorder 62 and wearable camera 10 detect mutualcommunication partners so that a communication link between in-carrecorder 62 and wearable camera 10 is established (step S1).Specifically, CPU 101 of in-car recorder 62 and MCU 19 of wearablecamera 10 detect communication partners by performing a pairing processby using, for example, SSIDs and passwords for the wireless LAN.

Wireless communicator 102 of in-car recorder 62 and communicator 21 ofwearable camera 10 exchange, for example, car IDs and officer IDs whichare respectively held therein, and the communication link is establishedin a case where the car IDs and the officer IDs held in a host deviceand a communication partner device respectively match each other.

Wireless communicator 102 of in-car recorder 62 and communicator 21 ofwearable camera 10 may establish the communication link when detectingcommunication partners without checking matching of the camera IDs andthe officer IDs. For example, in a case where police officer 7 is notlogging in to in-car PC 63, the camera ID and the officer ID are notinput to in-car recorder 62, and thus the camera ID and the officer IDare not held in in-car recorder 62.

Even in this case, the communication link can be established betweenin-car system 60 and wearable camera 10. For example, even in a casewhere combinations of police officer 7 and patrol car 6 at the time ofdispatch differ every time and thus are not fixed, in-car recorder 62and wearable camera 10 can be easily connected to each other by usingthe wireless LAN or the like.

In wearable camera 10, if a video recording starting trigger isdetected, MCU 19 starts recording of video data which is captured bycapture 11 and starts storing of the video data in storage 15 (step S2).

The video recording starting trigger in wearable camera 10 includes, forexample, detection of pressing of video recording switch SW1 or snapshotswitch SW2 in MCU 19, detection of cancelation of wireless connectionbetween in-car recorder 62 and wearable camera 10 in communicator 21,detection of an impact in the acceleration sensor (that is, detection ofa change in acceleration of a predetermined threshold value or greater),detection of police officer 7 being present in a predetermined area inGPS 18, and detection of police officer 7 starting to run in GPS 18. Thedetection of an impact in the acceleration sensor includes detection ofpolice officer 7 starting to run and falling.

Communicator 21 notifies in-car recorder 62 as a communication partnerof a video recording starting message (for example, a message “RECSTART”) including information indicating that video recording has beenstarted when MCU 19 starts recording of video data (step S3).

In in-car recorder 62, if wireless communicator 102 receives the videorecording starting message from wearable camera 10, CPU 101 startsrecording of video data which is captured by in-car camera 61 and startsstoring of the video data in SSD 111 (step S4).

As mentioned above, since video recording is started in in-car recorder62 in conjunction with video recording starting in wearable camera 10,for example, even in a case where police officer 7 arrives at scene 8,then an incident occurs, and video recording is not started by in-carcamera 61 in patrol car 6, video data of scene 8 can be recorded byin-car camera 61 and be checked in the future.

After wearable camera 10 and in-car recorder 62 start video recording,if MCU 19 of wearable camera 10 detects a video recording stoppingtrigger, MCU 19 stops recording of the video data captured by capture 11and stops storing of the video data in storage 15 (step S5). The videorecording stopping trigger in wearable camera 10 includes, for example,detection of pressing of video recording switch SW1 in MCU 19 duringvideo recording, and detection of a predetermined time period elapsingfrom the video recording starting in wearable camera 10.

Communicator 21 notifies in-car recorder 62 as a communication partnerof a video recording stopping message (for example, a message “RECSTOP”) including information indicating that the video recording hasstopped when MCU 19 stops recording of video data (step S6).

In in-car recorder 62, if wireless communicator 102 receives the videorecording stopping message from wearable camera 10, CPU 101 stopsrecording of the video data captured by in-car camera 61 and stopsstoring of the video data in SSD 111 (step S7).

As mentioned above, since video recording is stopped in in-car recorder62 in conjunction with video recording stoppage in wearable camera 10,for example, even in a case where police officer 7 forgets a pressingoperation of buttons 109 for stopping recording video data, video datacaptured by in-car camera 61 can be stopped from being recorded.Therefore, it is possible to reduce unnecessary power consumption orunnecessary use of the memory due to forgetfulness of stopping of videodata recording.

FIG. 27 exemplifies that wearable camera 10 stops video recording insteps S5 and S6, and in-car recorder 62 receives the video recordingstopping message and stops video recording in step S7. Alternatively,in-car recorder 62 may stop video recording and may transmit the videorecording stopping message in steps S5 and S6, and wearable camera 10may receive the video recording stopping message and may stop videorecording in step S7.

The processes in steps S5 to S7 may be omitted. In other words,cooperation for stopping video recording between wearable camera 10 andin-car recorder 62 may not be performed.

In wearable camera 10, after the video recording is started in step S2,MCU 19 assigns attribute information associated with video data, to thevideo data which is captured by capture 11 and is recorded by MCU 19(step S8). In the assignment of the attribute information, MCU 19 storesattribute information selected by using attribute selecting switch SW4in storage 15 in association with the video data recorded by wearablecamera 10.

If MCU 19 assigns the attribute information, communicator 21 notifiesin-car recorder 62 as a communication partner of an attributeinformation message including the attribute information (step S9).

In in-car recorder 62, wireless communicator 102 receives the attributeinformation message from wearable camera 10. CPU 101 assigns thereceived attribute information to video data which is captured by in-carcamera 61 and is recorded by in-car recorder 62 as attribute informationassociated with the video data (step S10). In the assignment of theattribute information, CPU 101 stores the attribute information (thatis, the attribute information selected by using attribute selectingswitch SW4) acquired from wearable camera 10 in SSD 111 in associationwith the video data recorded by in-car recorder 62. The respective videodata items assigned with the same attribute information in wearablecamera 10 and in-car recorder 62 are video data items which arerecorded, for example, in the same time zone or similar time zones.

FIG. 27 exemplifies that a notification of the attribute informationmessage is sent after wearable camera 10 stops video recording, but anotification of the attribute information message may be sent duringvideo recording in wearable camera 10.

As mentioned above, since in-car recorder 62 assigns attributeinformation in conjunction with assignment of attribute information inwearable camera 10, it is possible to save time and effort for policeofficer 7 to perform an input operation on in-car PC 63 in order toassign the attribute information in in-car recorder 62. Also in thiscase, police officer 7 can easily search for necessary video data in thefuture by using the assigned attribute information in the future.

Since a plurality of meta information pieces can be assigned to a singlevideo data item, a plurality of attribute information pieces can beassigned to the single video data item. In other words, both attributeinformation (for example, “trespass of real property”) which is inputvia in-car PC 63 and attribute information (for example, “stolenproperty”) corresponding to the operation of attribute informationassigning switch SW3 may be assigned to video data captured by in-carcamera 61. Consequently, wearable camera system 100 can discriminatecontent items of video data from each other with higher accuracy.

FIG. 28 is a sequence diagram illustrating a second example of anattribute information assigning procedure in wearable camera system 100.In FIG. 28, a case is assumed in which wearable camera 10 starts videorecording earlier than in-car recorder 62 and assigns attributeinformation earlier than in-car recorder 62. In the operation exampleillustrated in FIG. 28, the same processes in the operation exampleillustrated in FIG. 27 are given the same step numbers, and descriptionthereof will be omitted or will be made briefly. First, wearable camerasystem 100 performs processes in steps S1 to S7.

In in-car recorder 62, after the video recording is started in step S4,CPU 101 assigns attribute information associated with video data, to thevideo data which is captured by in-car camera 61 and is recorded byin-car recorder 62 (step S8A). In the assignment of the attributeinformation, CPU 101 stores attribute information which is input viain-car PC 63 in SSD 111 in association with the video data recorded byin-car recorder 62.

If CPU 101 assigns the attribute information, wireless communicator 102notifies wearable camera 10 as a communication partner of an attributeinformation message including the attribute information (step S9A).

In wearable camera 10, communicator 21 receives the attributeinformation message from in-car recorder 62. MCU 19 assigns the receivedattribute information to video data which is captured by capture 11 andis recorded by MCU 19 as attribute information associated with the videodata (step S10A). In the assignment of the attribute information, MCU 19stores the attribute information (that is, the attribute informationwhich is input via in-car PC 63) acquired from in-car recorder 62 instorage 15 in association with the video data recorded by wearablecamera 10. The respective video data items assigned with the sameattribute information in wearable camera 10 and in-car recorder 62 arevideo data items which are recorded, for example, in the same time zoneor similar time zones.

FIG. 28 exemplifies that a notification of the attribute informationmessage is sent after in-car recorder 62 stops video recording, but anotification of the attribute information message may be sent duringvideo recording in in-car recorder 62.

As mentioned above, since wearable camera 10 assigns attributeinformation in conjunction with assignment of attribute information inin-car recorder 62, it is possible to assign the attribute informationother than the attribute information allocated to attribute selectingswitch SW4 and thus to extend assignment of attribute information inwearable camera 10. Since in-car recorder 62 can assign more types ofattribute information than attribute information assigned by wearablecamera 10, it is possible to increase association between incidentcontent and assigned attribute information even in a case where theincident content in scene 8 does not match the attribute information inwearable camera 10, or details cannot be shown in the attributeinformation in wearable camera 10.

Since a plurality of meta information pieces can be assigned to a singlevideo data item, a plurality of attribute information pieces can beassigned to the single video data item. Both attribute information (forexample, “driving under the influence”) corresponding to the operationof attribute information assigning switch SW3 and attribute information(for example, “vandalism”) which is input via in-car PC 63 may beassigned to video data captured by wearable camera 10. Consequently,wearable camera system 100 can discriminate content items of video datafrom each other with higher accuracy. Instead of both of the attributeinformation pieces not being assigned, the attribute information whichis assigned by operating attribute information assigning switch SW3 maybe replaced with the attribute information which is input via in-car PC63.

FIG. 29 is a sequence diagram illustrating a third example of anattribute information assigning procedure in wearable camera system 100.In FIG. 29, a case is assumed in which wearable camera 10 starts videorecording later than in-car recorder 62 and assigns attributeinformation later than in-car recorder 62. In the operation exampleillustrated in FIG. 29, the same processes in the operation exampleillustrated in FIG. 27 or FIG. 28 are given the same step numbers, anddescription thereof will be omitted or will be made briefly.

First, wearable camera system 100 performs a process in step S1.

In in-car recorder 62, if a video recording starting trigger isdetected, CPU 101 starts recording of video data which is captured byin-car camera 61 and starts storing of the video data in SSD 111 (stepS2B).

The video recording starting trigger in in-car recorder 62 includes, forexample, detection of pressing of buttons 109, detection of starting oflighting and ringing of patrol lamps of patrol car 6 in CPU 101,detection of a traveling speed of patrol car 6 being equal to or higherthan a predetermined speed (for example, 100 km/h) in the speed sensor,detection of an impact in the acceleration sensor (that is, detection ofa change in acceleration of a predetermined threshold value or greater),and detection of being out of a communication range in whichcommunication between wireless communicator 102 and wearable camera 10cannot be performed.

Wireless communicator 102 notifies wearable camera 10 as a communicationpartner of a video recording starting message (for example, a message“REC START”) including information indicating that video recording hasstarted when CPU 101 starts recording of video data (step S3B).

In wearable camera 10, if communicator 21 receives the video recordingstarting message from in-car recorder 62, MCU 19 starts recording ofvideo data which is captured by capture 11 and starts storing of thevideo data in storage 15 (step S4B).

As mentioned above, since video recording is started in wearable camera10 in cooperation with video recording starting in in-car recorder 62,for example, even in a case where police officer 7 forgets a videorecording starting operation on video recording switch SW1 or snapshotswitch SW2 of wearable camera 10 due to emergency response, video dataof scene 8 can be recorded and be checked in the future.

For example, in a case where in-car recorder 62 and wearable camera 10have a long distance therebetween and are thus out of a communicationrange using the wireless LAN when a video recording starting trigger isdetected, in-car recorder 62 may transmit a video recording startingmessage after the wireless connection is recovered.

Wearable camera 10 may not start video recording immediately afterreceiving the video recording starting message. For example, wearablecamera 10 may not start video recording when the video recordingstarting message is received during traveling of patrol car 6, and maystart video recording when detecting that the wireless connection within-car recorder 62 is canceled due to becoming distant from patrol car6. Consequently, it is possible to use a resource of storage 15 whichaccumulates recorded video data, with high efficiency.

After in-car recorder 62 and wearable camera 10 start video recording,if CPU 101 of in-car recorder 62 detects a video recording stoppingtrigger, CPU 101 stops recording of the video data captured by in-carcamera 61 and stops storing of the video data in SSD 111 (step S5B).

The video recording stopping trigger in in-car recorder 62 includes, forexample, detection of pressing of buttons 109 in CPU 101 during videorecording, and detection of a predetermined time period elapsing fromthe video recording starting in in-car recorder 62.

Wireless communicator 102 notifies wearable camera 10 as a communicationpartner of a video recording stopping message (for example, a message“REC STOP”) including information indicating that the video recordinghas stopped when CPU 101 stops recording of video data (step S6B).

In wearable camera 10, if communicator 21 receives the video recordingstopping message from in-car recorder 62, MCU 19 stops recording of thevideo data captured by capture 11 and stops storing of the video data instorage 15 (step S7B).

As mentioned above, since video recording is stopped in wearable camera10 in cooperation with video recording stoppage in in-car recorder 62,for example, even in a case where police officer 7 forgets a videorecording stopping operation on video recording switch SW1 of wearablecamera 10 due to emergency response, video data of scene 8 can bestopped from being recorded. Therefore, it is possible to reduceunnecessary power consumption or unnecessary use of the memory due toforgetfulness of stopping of video data recording.

FIG. 29 exemplifies that in-car recorder 62 stops video recording andtransmits the video recording stopping message in steps S5B and S6B, andwearable camera 10 receives the video recording stopping message andstops video recording in step S7B. Alternatively, wearable camera 10 maystop video recording and may transmit the video recording stoppingmessage in steps S5B and S6B, and in-car recorder 62 may receive thevideo recording stopping message and may stop video recording in stepS7B.

The processes in steps S5B to S7B may be omitted. In other words,cooperation for stopping video recording between in-car recorder 62 andwearable camera 10 may not be performed.

For example, in a case where in-car recorder 62 and wearable camera 10have a long distance therebetween and are thus out of a communicationrange using the wireless LAN when a video recording stopping trigger isdetected, in-car recorder 62 may transmit a video recording stoppingmessage after the wireless connection is recovered.

Wearable camera system 100 performs processes in steps S8A to S10A aftervideo recording is started in step S2B.

In FIG. 29, there may be a plurality of wearable cameras 10 whichreceive a video recording starting message and start video recording.Similarly, there may be a plurality of wearable cameras 10 which receivea video recording stopping message and stop video recording. Similarly,there may be a plurality of wearable cameras 10 which receive anattribute information message and assign attribute information. Forexample, it is assumed that a plurality of police officers 7 ride inpatrol car 6.

FIG. 30 is a sequence diagram illustrating a fourth example of anattribute information assigning procedure in wearable camera system 100.In FIG. 30, a case is assumed in which wearable camera 10 starts videorecording later than in-car recorder 62 and assigns attributeinformation earlier than in-car recorder 62. In the operation exampleillustrated in FIG. 30, the same processes in the operation exampleillustrated in FIGS. 27 to 29 are given the same step numbers, anddescription thereof will be omitted or will be made briefly.

Wearable camera system 100 performs processes in steps S1 and S2B toS7B.

Wearable camera system 100 performs processes in steps S8 to S10 aftervideo recording is started in step S4B.

In FIG. 30, there may be a plurality of wearable cameras 10 whichreceive a video recording starting message and start video recording.Similarly, there may be a plurality of wearable cameras 10 which receivea video recording stopping message and stop video recording. Similarly,there may be a plurality of wearable cameras 10 which assign attributeinformation and notify the attribute information message. For example,it is assumed that a plurality of police officers 7 ride in patrol car6.

FIGS. 27 to 30 exemplify that attribute information is assigned bywearable camera 10 and in-car recorder 62, but some meta informationpieces including the attribute information or all of the metainformation pieces may be assigned. It is exemplified that acommunication partner is notified of an attribute information messageincluding attribute information, but a notification of a metainformation message including some meta information pieces including theattribute information or all of the meta information pieces may be sent.Consequently, wearable camera 10 and in-car recorder 62 can cooperatewith each other in relation to assignment of meta information.Therefore, for example, wearable camera 10 or in-car recorder 62 mayreceive an attribute information message or a meta information messageso as to add new meta information to a recorded video list held thereinor to update existing meta information.

As mentioned above, in the present exemplary embodiment, since wearablecamera 10 and in-car recorder 62 start video recording throughcooperation therebetween, the video recording can be started in responseto a video recording starting message from one of wearable camera 10 andin-car recorder 62 even in a case where the other of wearable camera 10and in-car recorder 62 does not start the video recording.

Therefore, for example, even in a case where police officer 7 hurriesfor an emergency response and thus forgets an input operation on videorecording switch SW1 of wearable camera 10 or cannot perform the inputoperation, wearable camera 10 can also start video recording if a videorecording starting trigger occurs in in-car recorder 62.

Since wearable camera 10 and in-car recorder 62 assign attributeinformation through cooperation therebetween, the attribute informationcan be assigned in response to an attribute information message from oneof wearable camera 10 and in-car recorder 62 even in a case where theother of wearable camera 10 and in-car recorder 62 does not assign theattribute information. In a case where in-car recorder 62 uses attributeinformation assigned by wearable camera 10, it is not necessary to inputattribute information via in-car PC 63. In a case where wearable camera10 uses attribute information assigned by in-car recorder 62, it ispossible to increase variations of attribute information which can beassigned by wearable camera 10 and thus to extend the attributeinformation assigning function of wearable camera 10.

As mentioned above, according to wearable camera system 100, it ispossible to improve convenience of handling video data captured bywearable camera 10. It is possible to easily search for and extractvideo data which is captured by wearable camera 10 or in-car camera 61by using attribute information and thus to improve performance ofmonitoring scene 8 or evidence performance of the video data.

As mentioned above, wearable camera system 100 of the present exemplaryembodiment includes wearable camera 10 which can be mounted on a user,in-car recorder 62 which is equipped in a vehicle in which the userrides, and in-car camera 61 which is equipped in the vehicle. In-carcamera 61 includes a first capture which captures videos. In-carrecorder 62 includes a first communicator which performs communicationwith wearable camera 10 as a communication partner; a first recorderwhich records first video data captured by in-car camera 61; and a firstinformation assigner which assigns first attribute informationassociated with the first video data to the first video data. Wearablecamera 10 includes a second capture which captures videos; a secondcommunicator which performs communication with in-car recorder 62 as acommunication partner; a second recorder which records second video datacaptured by the second capture; and a second information assigner whichassigns second attribute information associated with the second videodata to the second video data.

Wearable camera 10 starts video recording by using the second recorder,assigns the second attribute information to the second video data, andtransmits the second attribute information to in-car recorder 62. In-carrecorder 62 receives the second attribute information, and assigns thesecond attribute information to the first video data as the firstattribute information. Alternatively, in-car recorder 62 starts videorecording by using the first recorder, assigns the first attributeinformation to the first video data, and transmits the first attributeinformation to wearable camera 10. Wearable camera 10 receives the firstattribute information, and assigns the first attribute information tothe second video data as the second attribute information.

The first communicator is, for example, wireless communicator 102 orwired communicator 103. The first recorder is, for example, CPU 101. Thefirst information assigner is, for example, CPU 101. The second captureis, for example, capture 11. The second recorder is, for example, MCU19. The second information assigner is, for example, MCU 19. The useris, for example, police officer 7. The vehicle is, for example, patrolcar 6.

Consequently, since wearable camera 10 and in-car recorder 62 assignattribute information through cooperation therebetween, one of wearablecamera 10 and in-car recorder 62 can assist the other thereof in theoperation of assigning the attribute information, and thus assignment ofthe attribute information in both of the devices can be simplified. Forexample, by using attribute information assigned by wearable camera 10as attribute information assigned by in-car recorder 62, the user canomit an input operation on an input device (for example, in-car PC 63).For example, by using attribute information assigned by in-car recorder62 as attribute information assigned by wearable camera 10, it ispossible to assign many types of attribute information in wearablecamera 10. Therefore, wearable camera system 100 can improve convenienceof handling video data captured by wearable camera 10 or in-car camera61.

In wearable camera system 100, one of in-car recorder 62 and wearablecamera 10 may transmit video recording starting information includinginformation indicating that video recording has been started to theother of in-car recorder 62 and wearable camera 10 when one of in-carrecorder 62 and wearable camera 10 starts the video recording. The otherof in-car recorder 62 and wearable camera 10 may start the videorecording after the video recording starting information is received.

Consequently, since wearable camera 10 and in-car recorder 62 startvideo recording through cooperation therebetween, one of wearable camera10 and in-car recorder 62 can assist the other thereof in the videorecording operation, and thus video data can be reliably recorded inboth of the devices. Thus, wearable camera system 100 can improveconvenience of handling video data captured by wearable camera 10 andcan thus reduce recording omission of the video data. Therefore, forexample, it is possible to improve monitoring performance of wearablecamera system 100 or evidence performance of video data.

In wearable camera system 100, in-car recorder 62 may acquire the firstattribute information from an input device via which the first attributeinformation is input. Wearable camera 10 may include an operator whichreceives an operation of assigning the second attribute information. Theinput device is, for example, in-car PC 63. The operator is, forexample, attribute information assigning switch SW3.

Consequently, wearable camera system 100 can share attribute informationwhich is input by using different input methods with different devicesand can thus share convenience with the different devices.

In wearable camera system 100, the types of first attribute informationmay be more than the types of second attribute information.

Consequently, it is possible to assign attribute information in whichcontent of video data is reflected more accurately by using the in-carrecorder and thus to provide the attribute information to wearablecamera 10.

In wearable camera system 100, wearable camera 10 may assign both of thefirst attribute information received from in-car recorder 62 and thesecond attribute information received by the operator to the secondvideo data.

Consequently, since a plurality of attribute information pieces assignedby in-car recorder 62 and wearable camera 10 can be associated with asingle video data item, it is possible to assign the multilateralattribute information to the video data. Therefore, wearable camerasystem 100 can designate attribute information from various viewpointsin the future and search for or extract video data by using theattribute information.

In wearable camera system 100, in-car recorder 62 may assign both of thesecond attribute information received from wearable camera 10 and thefirst attribute information acquired from the input device to the firstvideo data.

Consequently, since a plurality of attribute information pieces assignedby in-car recorder 62 and wearable camera 10 can be associated with asingle video data item, it is possible to assign the multilateralattribute information to the video data. Therefore, wearable camerasystem 100 can designate attribute information from various viewpointsin the future and search for or extract video data by using theattribute information.

The attribute information assigning method of the present exemplaryembodiment is a method for wearable camera system 100 including wearablecamera 10 which can be mounted on a user, in-car recorder 62 which isequipped in a vehicle in which the user rides, and in-car camera 61which is equipped in the vehicle. The attribute information assigningmethod includes a step of causing in-car camera 61 to capture videos;causing wearable camera 10 to capture videos; a first video recordingstep of causing in-car recorder 62 to record first video data capturedby in-car camera 61; a second video recording step of causing wearablecamera 10 to record second video data captured by wearable camera 10; afirst information assigning step of assigning first attributeinformation associated with the first video data to the first videodata; a second information assigning step of assigning second attributeinformation associated with the second video data to the second videodata; and a communication step of performing communication betweenin-car recorder 62 and wearable camera 10.

In the attribute information assigning method, recording of the secondvideo data is started in the second video recording step, then thesecond attribute information is assigned to the second video data in thesecond information assigning step, the second attribute information istransmitted from wearable camera 10 to in-car recorder 62 in thecommunication step, and the second attribute information is assigned tothe first video data as the first attribute information in the firstinformation assigning step. Alternatively, in the attribute informationassigning method, recording of the first video data is started in thefirst video recording step, then the first attribute information isassigned to the first video data in the first information assigningstep, the first attribute information is transmitted from in-carrecorder 62 to wearable camera 10 in the communication step, and thefirst attribute information is assigned to the second video data as thesecond attribute information in the second information assigning step.

Consequently, since wearable camera 10 and in-car recorder 62 assignattribute information through cooperation therebetween, one of wearablecamera 10 and in-car recorder 62 can assist the other thereof in theoperation of assigning the attribute information, and thus assignment ofthe attribute information in both of the devices can be simplified. Forexample, by using attribute information assigned by wearable camera 10as attribute information assigned by in-car recorder 62, the user canomit an input operation on an input device (for example, in-car PC 63).For example, by using attribute information assigned by in-car recorder62 as attribute information assigned by wearable camera 10, it ispossible to assign many types of attribute information in wearablecamera 10. Therefore, wearable camera system 100 can improve convenienceof handling video data captured by wearable camera 10 or in-car camera61.

As mentioned above, various embodiments have been described withreference to the drawings, but the present invention is not limited tothe embodiments. It is clear that a person skilled in the art canconceive of various modifications or alterations within the scoperecited in the claims, and it is understood that they naturally fallwithin the technical scope of the present invention. The respectiveconstituent elements in the above-described embodiments may bearbitrarily combined with each other within the scope without departingfrom the spirit of the present invention.

What is claimed is:
 1. A wearable camera comprising: a capture that captures video; an acceleration sensor; a recorder that records video data captured by the capture; a video recording switch, operation of which causes the recorder to record video data captured by the capture; and a storage that stores a recording starting factor generated from at least the acceleration sensor or the video recording switch.
 2. The wearable camera of claim 1, wherein, when the acceleration sensor detects a change in acceleration of a predetermined threshold value or greater, recording of the video data by the recorder is started.
 3. The wearable camera of claim 1, further comprising: a GPS receiver that receives current positional information of the wearable camera, wherein the current positional information is a recording starting factor, and the storage stores a recording starting factor generated from at least the acceleration sensor, the video recording switch or the GPS receiver.
 4. The wearable camera of claim 1, wherein operation of the video recording switch causes starting or stoppage of the capture according to number of inputs received by the video recording switch.
 5. The wearable camera of claim 1, wherein the video recording switch operates starting or stoppage of the capture according to number of inputs received by the video recording switch.
 6. A method for using a wearable camera, the method comprising: capturing video by a capture of the wearable camera; detecting acceleration of the wearable camera using an acceleration sensor of the wearable camera; operating a video recording switch of the wearable camera to cause recording of video captured by the wearable camera; recording video data captured by the capture of the wearable camera; and storing a recording starting factor generated from at least the acceleration sensor or the video recording switch.
 7. The method of claim 6, wherein the detecting acceleration includes detecting that the acceleration of the wearable camera is a predetermined threshold or greater and starting the recording upon detecting the acceleration of the wearable camer is a predetermined threshold or greater.
 8. The method of claim 6, wherein the storing a recording starting factor includes storing a recording starting factor generated from the video recording switch.
 9. The method of claim 6, further comprising: receiving at a GPS receiver of the wearable camera, current positional information of the wearable camera; and storing the current positional information as the recording starting factor.
 10. The method of claim 9, further comprising starting the recording video data based on the received current positional information. 